Skip to contentSkip to conversation

another i2c/for-next branch

DISCUSSION Wolfram Sang 4 participants 4 messages Mar 2, 2012 – Mar 4, 2012 I2C subsystem host drivers

lore
Share & tools
lore
#0 lore raw

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

Signature · 2 lines
Pengutronix e.K.                           | Wolfram Sang                |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
#1 lore raw
Quoted 6 lines · Wolfram Sang

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!

Signature · 1 line
Jean Delvare
#2 lore raw
Quoted 10 lines · Jean Delvare
Quoted 6 lines · Wolfram Sang

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.

Signature · 3 lines
Ben Dooks, [email protected], http://www.fluff.org/ben/

Large Hadron Colada: A large Pina Colada that makes the universe disappear.
#3 lore raw
In reply to Wolfram Sang

Hi Wolfram,

Quoted 5 lines · On Fri, 2 Mar 2012 14:43:05 +0100 Wolfram Sang…

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.

Signature · 15 lines
Cheers,
Stephen Rothwell 
[email protected]

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.