another i2c/for-next branch

another i2c/for-next branch

[Wolfram Sang]

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

Hi Stephen,

I am also collecting patches for the i2c-subsystem. Can you add my branch to
linux-next, please?

git://git.pengutronix.de/git/wsa/linux.git i2c-embedded/for-next

Thanks in advance,

   Wolfram

-- 
Pengutronix e.K.                           | Wolfram Sang                |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |

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

Re: another i2c/for-next branch

[Jean Delvare]

On Fri, 2 Mar 2012 14:43:05 +0100, Wolfram Sang wrote:
> Hi Stephen,
> 
> I am also collecting patches for the i2c-subsystem. Can you add my branch to
> linux-next, please?
> 
> git://git.pengutronix.de/git/wsa/linux.git i2c-embedded/for-next

Would be good to have this in linux-next, yes. Thanks Wolfram for your
help!

-- 
Jean Delvare

Re: another i2c/for-next branch

[Ben Dooks]

On Fri, Mar 02, 2012 at 03:11:18PM +0100, Jean Delvare wrote:
> On Fri, 2 Mar 2012 14:43:05 +0100, Wolfram Sang wrote:
> > Hi Stephen,
> > 
> > I am also collecting patches for the i2c-subsystem. Can you add my branch to
> > linux-next, please?
> > 
> > git://git.pengutronix.de/git/wsa/linux.git i2c-embedded/for-next
> 
> Would be good to have this in linux-next, yes. Thanks Wolfram for your
> help!

Seconded, Thankyou. I have asked Wolfram to handle things for this merge
window as I am currently too busy to give adequate time to it.

-- 
Ben Dooks, ben@fluff.org, http://www.fluff.org/ben/

Large Hadron Colada: A large Pina Colada that makes the universe disappear.

Re: another i2c/for-next branch

[Stephen Rothwell]

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

Hi Wolfram,

On Fri, 2 Mar 2012 14:43:05 +0100 Wolfram Sang <w.sang@pengutronix.de> wrote:
>
> I am also collecting patches for the i2c-subsystem. Can you add my branch to
> linux-next, please?
> 
> git://git.pengutronix.de/git/wsa/linux.git i2c-embedded/for-next

I have added that from today with 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 --]