From: James Morris <jmorris@namei.org>
To: Micah Morton <mortonm@chromium.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 04:03:33 +1000 (AEST) [thread overview]
Message-ID: <alpine.LRH.2.21.2006160403190.9951@namei.org> (raw)
In-Reply-To: <CAJ-EccO+4s8Dd=wj75ckfp4ZLhppt7uCgg2chf4SvTOxzqbgPw@mail.gmail.com>
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.
>
> >
> > --
> > James Morris
> > <jmorris@namei.org>
> >
>
--
James Morris
<jmorris@namei.org>
next prev parent reply other threads:[~2020-06-15 18:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-09 18:26 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 [this message]
2020-06-16 16:35 ` Micah Morton
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=alpine.LRH.2.21.2006160403190.9951@namei.org \
--to=jmorris@namei.org \
--cc=casey@schaufler-ca.com \
--cc=john.johansen@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=mortonm@chromium.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®