Hi Jason, On Thu, 20 Oct 2022 15:01:14 -0600 "Jason A. Donenfeld" <Jason@xxxxxxxxx> wrote: > > I'm working on some potentially disruptive changes that could really > benefit from being in -next. Linus suggested I accumulate these > changes in a separate branch for that. Currently that's here: > > https://git.kernel.org/pub/scm/linux/kernel/git/zx2c4/linux.git branch > unsigned-char > > I'm not sure how automated your setup is. Would it make sense to add > that branch explicitly, or to add a "for-next" branch/tag, which you > can grab if it exists and skip if it's gone? Added form today. Just keep that branch updated and I will refetch it periodically (at least daily during the week). If it is not there I will keep using whatever was there last time I fetched until you tell me to remove it from -next. 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:
pgp6iRCYUuEn3.pgp
Description: OpenPGP digital signature
