Hi Philipp, On Mon, 29 May 2017 15:23:17 +0200 Philipp Zabel <p.zabel@xxxxxxxxxxxxxx> wrote: > > could you add the reset/next and reset/fixes branches to the linux-next > tree? I use those to stage reset framework and driver patches before > sending them off to be merged via arm-soc. > > https://git.pengutronix.de/git/pza/linux reset/fixes > https://git.pengutronix.de/git/pza/linux reset/next Added from today. 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 -- To unsubscribe from this list: send the line "unsubscribe linux-next" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
