Hi Kees, On Wed, 23 Feb 2022 21:37:51 -0800 Kees Cook <keescook@xxxxxxxxxxxx> wrote: > > As part of Eric and I stepping up to officially[1] be the execve and > binfmt maintainers, please add my for-next/execve tree to linux-next: > > https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git/log/?h=for-next/execve > > This tree currently contains all the exec and binfmt patches from mmotm > as well as at least one newly reviewed change[2]. > > [1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/MAINTAINERS?h=v5.17-rc1#n7223 > [2] https://lore.kernel.org/lkml/164486710836.287496.5467210321357577186.b4-ty@xxxxxxxxxxxx/ Added from today (Mark added it earlier to his tree). 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 -- Cheers, Stephen Rothwell
Attachment:
pgpuciWP1o3sf.pgp
Description: OpenPGP digital signature
