Hi Dan,
On Fri, 10 Feb 2012 10:59:25 -0800 Dan Williams <dan.j.williams@xxxxxxxxx> wrote:
>
> I have a couple of active topic branches brewing for 3.4 that address
> problems in libsas as well as ongoing development of the libsas-based
> isci driver. They are at the point where they should be getting
> exposure in -next, so I have combined them into a daily-merge branch
> 'all' for linux-next consumption.
>
> git://git.kernel.org/pub/scm/linux/kernel/git/djbw/isci.git all
I have added this from today.
> For at least the next few weeks I would like to have this tree in -next.
> This gives James the option of letting these brew with -next exposure
> before applying the patches, or just pulling the git topics directly for
> the merge window. If this tree ever develops a conflict with scsi-misc
> -next should drop it as that probably means the patches have started
> making their way into scsi-misc.
I try my best to not drop trees because that will screw up Andrew's work,
if nothing else. And with any luck, James will actually merge your
branches rather than apply your patches and thus we will get no
conflicts ...
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@xxxxxxxxxxxxxxxx
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.
Attachment:
pgp2i16aHND4i.pgp
Description: PGP signature
