Add SafeSetID LSM tree to linux-next
Micah Morton
mortonm at chromium.org
Mon Jun 15 23:10:36 UTC 2020
On Mon, Jun 15, 2020 at 3:53 PM Stephen Rothwell <sfr at canb.auug.org.au> wrote:
>
> Hi Micah,
>
> On Mon, 15 Jun 2020 13:26:33 -0700 Micah Morton <mortonm at chromium.org> wrote:
> >
> > Could you add my safesetid-next branch from my tree to linux-next? It
> > can be found here:
> > https://github.com/micah-morton/linux.git#safesetid-next
> >
> > Let me know if there is anything else I need to do.
>
> Added from today.
Sounds good, thanks!
>
> 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 at canb.auug.org.au
More information about the Linux-security-module-archive
mailing list