Hi Daniel, On Mon, 17 Dec 2018 16:42:53 +0000 Daniel Thompson <daniel.thompson@xxxxxxxxxx> wrote: > > Is there any change you could add my kgdb tree to the roster for > linux-next : > > https://git.kernel.org/pub/scm/linux/kernel/git/danielt/linux.git kgdb/for-next > > I'm currently collecting kgdb patches for v4.21 together and at the > moment it looks like the PR for kgdb will come from my tree this dev > cycle. > > This will leave you with two kgdb trees in this list which I assume > isn't great for you (although Jason's tree isn't really changing much > at the moment so I guess merging it is a nop). Anyhow I've made a diary > note to follow this up in two kernel cycles time and decide which one > we want to keep on the roster. Is that OK for you? Added from today. I called it kgdb-dt but that can be changed if you decide to replace Jason's tree with this one. 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. -- Cheers, Stephen Rothwell sfr@xxxxxxxxxxxxxxxx
Attachment:
pgpI8T8ruQ3i2.pgp
Description: OpenPGP digital signature
