Skip to contentSkip to conversation

Pull Request for linux-next

DISCUSSION Tobin C. Harding 2 participants 3 messages Feb 25, 2018

lore
Share & tools
lore
#0 lore raw

Hi Stephen,

Would it be possible to get the development tree for scripts/leaking_addresses.pl included in Linux-next please.

The tree is hosted on kernel.org

https://git.kernel.org/pub/scm/linux/kernel/git/tobin/leaks.git/

I have created a branch called linux-next. This branch is not tagged or signed. I'm super new to kernel maintainer branch management, ATM the tree mirrors GregKH's staging tree setup i.e 3 branches

master
leaks-testing
leaks-next

Development done on leaks-testing. Once patches have been rinsed through LKML move them to leaks-next. Any holes in that?

thanks,
Tobin.

#1 lore raw

Hi Tobin,

Quoted 12 lines · On Sun, 25 Feb 2018 18:59:07 +1100 "Tobin C. Harding" <[email protected]> wrote:

Would it be possible to get the development tree for scripts/leaking_addresses.pl included in Linux-next please.

The tree is hosted on kernel.org

https://git.kernel.org/pub/scm/linux/kernel/git/tobin/leaks.git/

I have created a branch called linux-next. This branch is not tagged or signed. I'm super new to kernel maintainer branch management, ATM the tree mirrors GregKH's staging tree setup i.e 3 branches

Quoted 6 lines

master
leaks-testing
leaks-next

Development done on leaks-testing. Once patches have been rinsed through LKML move them to leaks-next. Any holes in that?

That looks fine to me. I have added your leaks-next branch from today. It would be nice to see some Reviewed-by or Acked-by tags on your commits.

Thanks for adding your subsystem tree as a participant of linux-next. As you may know, this is not a judgement 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
Quoted 19 lines · Stephen Rothwell

Hi Tobin,

Quoted 16 lines · On Sun, 25 Feb 2018 18:59:07 +1100 "Tobin C. Harding" <[email protected]> wrote:

Would it be possible to get the development tree for scripts/leaking_addresses.pl included in Linux-next please.

The tree is hosted on kernel.org

https://git.kernel.org/pub/scm/linux/kernel/git/tobin/leaks.git/

I have created a branch called linux-next. This branch is not tagged or signed. I'm super new to kernel maintainer branch management, ATM the tree mirrors GregKH's staging tree setup i.e 3 branches

master
leaks-testing
leaks-next

Quoted 6 lines
Quoted 2 lines

Development done on leaks-testing. Once patches have been rinsed through LKML move them to leaks-next. Any holes in that?

That looks fine to me. I have added your leaks-next branch from today. It would be nice to see some Reviewed-by or Acked-by tags on your commits.

Yeah I know that would be awesome, there doesn't seem to be a lot of interest in this script ATM. None of my recent patches have gotten any comments what so ever. We have a second maintainer now though so hopefully there will be at least two sets of eyes going over it.

Quoted 2 lines

Thanks for adding your subsystem tree as a participant of linux-next. As you may know, this is not a judgement of your code.

lol, that line made my heart jump into mouth ready for the comment to come :)

Quoted 13 lines

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 2 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.

Cheers,
Tobin.