Please add for-next/execve

Please add for-next/execve

[Kees Cook]

Hello!

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@chromium.org/

-- 
Kees Cook

Re: Please add for-next/execve

[Matthew Wilcox]

On Wed, Feb 23, 2022 at 09:37:51PM -0800, Kees Cook 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].

Hey Kees, Stephen's on holiday this week.  Mark's stepping into his
shoes for another couple of days.

Re: Please add for-next/execve

[Mark Brown]

[-- Attachment #1: Type: text/plain, Size: 779 bytes --]

On Thu, Feb 24, 2022 at 08:20:56PM +0000, Matthew Wilcox wrote:
> On Wed, Feb 23, 2022 at 09:37:51PM -0800, Kees Cook 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].

> Hey Kees, Stephen's on holiday this week.  Mark's stepping into his
> shoes for another couple of days.

I'll give importing this ago tomorrow for my final attempt of the week
at -next, you should make sure that Stephen picks it up when he gets
back though.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

Re: Please add for-next/execve

[Stephen Rothwell]

[-- Attachment #1: Type: text/plain, Size: 1627 bytes --]

Hi Kees,

On Wed, 23 Feb 2022 21:37:51 -0800 Kees Cook <keescook@chromium.org> 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@chromium.org/

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@canb.auug.org.au

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]