Next: please switch the GPIO tree to mine

Next: please switch the GPIO tree to mine

[Linus Walleij]

Hi Stephen,

Grant asked me to take over the GPIO tree for a while.
(See: https://lkml.org/lkml/2012/7/1/220)

Can you please replace Grants tree:
gpio-current    git     git://git.secretlab.ca/git/linux-2.6#gpio/merge

With this one:
gpio git git://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-gpio.git#for-next

Until further notice.

I have a few patches for the rc:s there, as well as some stuff for the
next merge window, so would be really nice to get some rotation on
this.

Thanks!
Linus Walleij

Re: Next: please switch the GPIO tree to mine

[Linus Walleij]

On Thu, Jul 5, 2012 at 4:42 PM, Grant Likely <grant.likely@secretlab.ca> wrote:
> On Jul 5, 2012 8:04 AM, "Linus Walleij" <linus.walleij@linaro.org> wrote:
>>
>> Hi Stephen,
>>
>> Grant asked me to take over the GPIO tree for a while.
>> (See: https://lkml.org/lkml/2012/7/1/220)
>>
>> Can you please replace Grants tree:
>> gpio-current    git     git://git.secretlab.ca/git/linux-2.6#gpio/merge
>>
>> With this one:
>> gpio git
>> git://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-gpio.git#for-next
>>
>> Until further notice.
>
> Actually, don't replace mine. Just add Linus' as another GPIO tree.

I pulled your gpio/merge tag into my tree so all is in one place though.

But git will cope I guess so no big deal.

Yours,
Linus Walleij

Re: Next: please switch the GPIO tree to mine

[Stephen Rothwell]

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

Hi Linus,

On Thu, 5 Jul 2012 16:04:09 +0200 Linus Walleij <linus.walleij@linaro.org> wrote:
>
> Grant asked me to take over the GPIO tree for a while.
> (See: https://lkml.org/lkml/2012/7/1/220)
> 
> Can you please replace Grants tree:
> gpio-current    git     git://git.secretlab.ca/git/linux-2.6#gpio/merge
> 
> With this one:
> gpio git git://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-gpio.git#for-next

I have added this tree (as requested by Grant) from today.  I called it
gpio-lw with just you as the contact.

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