Re: linux-next: Tree for Mar 7

[Stephen Rothwell <sfr@canb.auug.org.au>]

[-- Attachment #1: Type: text/plain, Size: 3783 bytes --]

Hi "Jörn",

On Tue, 12 Mar 2013 19:33:11 -0400 Jörn Engel <joern@logfs.org> wrote:
>
> On Wed, 13 March 2013 11:11:44 +1100, Stephen Rothwell wrote:
> > On Tue, 12 Mar 2013 14:44:22 -0400 Jörn Engel <joern@logfs.org> wrote:
> > >
> > > Any chance to get the bcon tree included?
> > > 
> > > git://git.kernel.org/pub/scm/linux/kernel/git/joern/bcon2.git
> > 
> > Well, maybe you could tell me something about that tree i.e. what is in
> > it, why I should merge it, how it will be sent to Linus ... also what
> > branch to fetch and who should be contacted about conflicts, build
> > problems etc.
> 
> What is in it:
> - Mainly blockconsole, a console driver that will write printk
>   messages to block devices.  Very useful when netconsole, for
>   whatever reasons, is not available.  Code is originally from April
>   last year and by now we have upwards of 100 machines running it.
>   A number of bugs were identified because of it.
> - Also a patchset to disable the loglevel filtering for
>   non-interactive consoles like blockconsole and netconsole.  Again,
>   we run it across the board and real bugs were fixed because of it.
> 
> Why should you merge it:
> I plan to send this to Linus in the next merge window.
> 
> How will it be sent to Linus:
> Merge request, unless someone finds a good reason against it.
> 
> What branch:
> master.  I personally don't use branches at all, at least not
> consciously.
> 
> Who should be contacted about conflicts, etc:
> Me.
> 
> > Also consider: is this stuff ready for inclusion in Linus' tree (maybe
> > apart from integration conflicts), is it well reviewed/tested?
> 
> Two people from SuSE seem to find the code useful and have provided
> testing and patches.  To the best of my knowledge this code is ready
> to go and useful for more people that just me or $EMPLOYER.
> 
> I will be giving a talk at the collaboration summit that is
> essentially going to cover this tree.  Conferences have a lower bar
> for acceptance than Linus does, but at least it must have caught
> someone's interest.

Added from today.

One thing, the last few commits from Takashi do not have your
Signed-off-by even though you committed them.

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@canb.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.

[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]