linux-kernel - Re: Including drm-intel tree to linux-next

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20130215102734.0ebe1b4826e94c83ed7a407d@canb.auug.org.au>
Date:	Fri, 15 Feb 2013 10:27:34 +1100
From:	Stephen Rothwell <sfr@...b.auug.org.au>
To:	Daniel Vetter <daniel.vetter@...ll.ch>
Cc:	Borislav Petkov <bp@...en8.de>, rostedt@...dmis.org,
	Dave Airlie <airlied@...il.com>,
	dri-devel <dri-devel@...ts.freedesktop.org>,
	intel-gfx <intel-gfx@...ts.freedesktop.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Including drm-intel tree to linux-next

Hi Daniel,

On Thu, 14 Feb 2013 15:19:53 +0100 Borislav Petkov <bp@...en8.de> wrote:
>
> On Thu, Feb 14, 2013 at 03:12:02PM +0100, Daniel Vetter wrote:
> > 
> > Since about a year ago we've switched drm/i915 to buffer around 2
> > weeks worth of patches so that we can do decent QA before breaking
> > everyone's tree when things land in Dave's drm-next. But that also
> > means we'll miss out a bit in the integration testing -next provides,
> > which did hurt a bit in recent efforts. Hence can you please include
> > 
> > git://people.freedesktop.org/~danvet/drm-intel drm-intel-next-queued
> > 
> > into linux-next? Probably best to merge it after drm-next. Note that
> > drm-intel-next are the QA'ed chunks I send off to Dave. Also, any
> > mailing lists I'm supposed to follow? And if possible please cc
> > intel-gfx@...ts.freedesktop.org besides dri-devel/lkml when conflicts
> > with that tree pop up (you won't get moderation spam any more, we've
> > fixed that up).

Added from today.  I am in two minds a bit since I really like stuff in
linux-next to have been reviewed and debugged as much as possible.   But
I have added it and will keep an eye on how many problems it causes.

Problem reports will go to you, intel-gfx and dri-devel.  You can follow
linux-next@...r.kernel.org (I sometimes post stuff there that goes
nowhere else (except lkml - which noone seems to notice :-)).

Thanks for adding your subsystem tree as a participant of linux-next.  As
you may know, this is not a judgment of your code.  The purpose of
linux-next is for integration testing and to lower the impact of
conflicts between subsystems in the next merge window. 

You will need to ensure that the patches/commits in your tree/series have
been:
     * submitted under GPL v2 (or later) and include the Contributor's
	Signed-off-by,
     * posted to the relevant mailing list,
     * reviewed by you (or another maintainer of your subsystem tree),
     * successfully unit tested, and 
     * destined for the current or next Linux merge window.

Basically, this should be just what you would send to Linus (or ask him
to fetch).  It is allowed to be rebased if you deem it necessary.

-- 
Cheers,
Stephen Rothwell 
sfr@...b.auug.org.au

Legal Stuff:
By participating in linux-next, your subsystem tree contributions are
public and will be included in the linux-next trees.  You may be sent
e-mail messages indicating errors or other issues when the
patches/commits from your subsystem tree are merged and tested in
linux-next.  These messages may also be cross-posted to the linux-next
mailing list, the linux-kernel mailing list, etc.  The linux-next tree
project and IBM (my employer) make no warranties regarding the linux-next
project, the testing procedures, the results, the e-mails, etc.  If you
don't agree to these ground rules, let me know and I'll remove your tree
from participation in linux-next.

Content of type "application/pgp-signature" skipped