From: Micah Morton <mortonm@chromium.org>
To: James Morris <jmorris@namei.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-security-module <linux-security-module@vger.kernel.org>,
Paul Moore <paul@paul-moore.com>,
Casey Schaufler <casey@schaufler-ca.com>,
John Johansen <john.johansen@canonical.com>
Subject: Re: [GIT PULL] SafeSetID LSM changes for v5.8
Date: Tue, 16 Jun 2020 09:35:54 -0700 [thread overview]
Message-ID: <CAJ-EccNrw6J0-Z2qAMpAT4YUZMmuAN8P33SjN6tGOjekYHggGw@mail.gmail.com> (raw)
In-Reply-To: <alpine.LRH.2.21.2006160403190.9951@namei.org>
On Mon, Jun 15, 2020 at 11:03 AM James Morris <jmorris@namei.org> wrote:
>
> On Mon, 15 Jun 2020, Micah Morton wrote:
>
> > On Sun, Jun 14, 2020 at 10:21 PM James Morris <jmorris@namei.org> wrote:
> > >
> > > On Sun, 14 Jun 2020, Micah Morton wrote:
> > >
> > > > This patch was sent to the security mailing list and there were no objections.
> > >
> > > Standard practice for new or modified LSM hooks is that they are reviewed
> > > and acked by maintainers of major LSMs (SELinux, AppArmor, and Smack, at
> > > least).
> > >
> > > "No objections" should be considered "not reviewed".
> > >
> > > Can you add your tree to linux-next?
> > > https://www.kernel.org/doc/man-pages/linux-next.html
> >
> > Sure, I can do that. I should just send an email to Stephen Rothwell
> > asking him to include the -next branch from my tree?
>
> Yep, thanks.
The commit is in -next as of next-20200615
Thanks
>
> >
> > >
> > > --
> > > James Morris
> > > <jmorris@namei.org>
> > >
> >
>
> --
> James Morris
> <jmorris@namei.org>
>
prev parent reply other threads:[~2020-06-16 16:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-09 18:26 [GIT PULL] SafeSetID LSM changes for v5.8 Micah Morton
2020-06-12 21:23 ` Linus Torvalds
2020-06-14 18:03 ` Micah Morton
2020-06-14 18:39 ` Linus Torvalds
2020-06-14 19:12 ` Micah Morton
2020-06-14 19:20 ` Linus Torvalds
2020-06-15 16:28 ` Micah Morton
2020-06-14 18:55 ` pr-tracker-bot
2020-06-15 5:21 ` James Morris
2020-06-15 16:22 ` Micah Morton
2020-06-15 18:03 ` James Morris
2020-06-16 16:35 ` Micah Morton [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAJ-EccNrw6J0-Z2qAMpAT4YUZMmuAN8P33SjN6tGOjekYHggGw@mail.gmail.com \
--to=mortonm@chromium.org \
--cc=casey@schaufler-ca.com \
--cc=jmorris@namei.org \
--cc=john.johansen@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=paul@paul-moore.com \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.