Skip to contentSkip to conversation

Request the EXTCON remote-tracking branch

DISCUSSION Stephen Rothwell 2 participants 2 messages Mar 11, 2015 – Mar 12, 2015 1 message not in the archive Linux-next tree

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

#1 lore raw

Hi Chanwoo,

Quoted 7 lines · On Wed, 11 Mar 2015 11:20:36 +0900 Chanwoo Choi <[email protected]> wrote:

I'm a maintainer of EXTCON (External Connector) subsystem. I want to merge latest extcon patch-set (extcon-next) to linux-next git repository for integration test.

EXTCON git repository:
- git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git (branch name : extcon-next)

That isn't really your repository, now is it? :-)

I used git://git.kernel.org/pub/scm/linux/kernel/git/chanwoo/extcon.git

I have added your tree from today.

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 · 3 lines
Cheers,
Stephen Rothwell 
[email protected]
#2 lore raw

Hi Stephen,

Quoted 8 lines · Stephen Rothwell

Hi Chanwoo,

Quoted 5 lines · On Wed, 11 Mar 2015 11:20:36 +0900 Chanwoo Choi <[email protected]> wrote:

I'm a maintainer of EXTCON (External Connector) subsystem. I want to merge latest extcon patch-set (extcon-next) to linux-next git repository for integration test.

Quoted 6 lines
Quoted 2 lines

EXTCON git repository:
- git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git (branch name : extcon-next)

That isn't really your repository, now is it? :-)

I used git://git.kernel.org/pub/scm/linux/kernel/git/chanwoo/extcon.git

You're right. I'm so sorry about wrong information of extcon.git respository.

Quoted 17 lines

I have added your tree from today.

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.

Quoted 3 lines

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.

Thanks for your effort.

Best Regards,
Chanwoo Choi