New Char/Misc tree to be added to linux-next

New Char/Misc tree to be added to linux-next

[Greg KH]

Hi Stephen,

Arnd and I are going to maintain the drivers/char/* and drivers/misc/*
directories with the goal of getting them under control, or at least a
false-sense of control :)

So could you please add my new git tree:
	git.kernel.org/pub/scm/linux/kernel/git/gregkh/char-misc.git

which contains the two branches, "char-misc-linus" to hold patches to
send to Linus for this merge window, and "char-misc-next" to hold
patches for the next merge window.

thanks,

greg k-h

Re: New Char/Misc tree to be added to linux-next

[Stephen Rothwell]

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

Hi Greg,

On Mon, 14 Nov 2011 16:14:19 -0800 Greg KH <greg@kroah.com> wrote:
>
> Arnd and I are going to maintain the drivers/char/* and drivers/misc/*
> directories with the goal of getting them under control, or at least a
> false-sense of control :)
> 
> So could you please add my new git tree:
> 	git.kernel.org/pub/scm/linux/kernel/git/gregkh/char-misc.git
> 
> which contains the two branches, "char-misc-linus" to hold patches to
> send to Linus for this merge window, and "char-misc-next" to hold
> patches for the next merge window.

OK, I will add this tree tomorrow with you and Arnd as contacts.  [Aside:
did you consider naming the branches merely "fixes" (or something) and
"next"?]

I guess there is actually quite a lot of scope for overlap with other
trees touching stuff in drivers/char ... just something to keep an eye on.

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 --]

Re: New Char/Misc tree to be added to linux-next

[Greg KH]

On Tue, Nov 15, 2011 at 12:59:39PM +1100, Stephen Rothwell wrote:
> Hi Greg,
> 
> On Mon, 14 Nov 2011 16:14:19 -0800 Greg KH <greg@kroah.com> wrote:
> >
> > Arnd and I are going to maintain the drivers/char/* and drivers/misc/*
> > directories with the goal of getting them under control, or at least a
> > false-sense of control :)
> > 
> > So could you please add my new git tree:
> > 	git.kernel.org/pub/scm/linux/kernel/git/gregkh/char-misc.git
> > 
> > which contains the two branches, "char-misc-linus" to hold patches to
> > send to Linus for this merge window, and "char-misc-next" to hold
> > patches for the next merge window.
> 
> OK, I will add this tree tomorrow with you and Arnd as contacts.  [Aside:
> did you consider naming the branches merely "fixes" (or something) and
> "next"?]

I was using the same branch naming that I used for my other trees.  If
that's unwieldy, I can easily change them, just let me know, but I would
like to be consistant across all of my trees for the sake of my muscle
memory, and my helper-scripts.

thanks,

greg k-h

Re: New Char/Misc tree to be added to linux-next

[Stephen Rothwell]

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

Hi Greg,

On Mon, 14 Nov 2011 22:01:02 -0800 Greg KH <greg@kroah.com> wrote:
>
> I was using the same branch naming that I used for my other trees.  If
> that's unwieldy, I can easily change them, just let me know, but I would
> like to be consistant across all of my trees for the sake of my muscle
> memory, and my helper-scripts.

No worries, I was just asking.  (*I* almost never type them myself)

-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/

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