From: James Morris <jmorris@namei.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Jiri Kosina <jikos@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
LSM List <linux-security-module@vger.kernel.org>,
Matthew Garrett <mjg59@google.com>,
David Howells <dhowells@redhat.com>
Subject: Re: [GIT PULL][SECURITY] Kernel lockdown patches for v5.4
Date: Mon, 30 Sep 2019 10:03:14 +1000 (AEST) [thread overview]
Message-ID: <alpine.LRH.2.21.1909301002020.22854@namei.org> (raw)
In-Reply-To: <CAHk-=wg=7y82dJYeLzQeup70CHBT7MpCC155d85cPFctNsxUYA@mail.gmail.com>
On Sat, 28 Sep 2019, Linus Torvalds wrote:
> On Fri, Sep 27, 2019 at 11:19 AM Linus Torvalds
> <torvalds@linux-foundation.org> wrote:
> >
> > This is one of the pull requests that I have to go through commit by
> > commit because of the history of this thing.
> >
> > And I've yet to empty my queue of all the _regular_ things that came
> > in this merge window, so I haven't had time.
>
> I've emptied my queue (well, in the meantime I got new pull requests,
> but what else is new..) and went through the security pulls yesterday
> and this morning, and found nothing objectionable.
>
> So it's merged now.
Thanks.
Matthew has agreed to maintain this code now that it's merged.
Matthew: please submit a maintainer entry for this.
--
James Morris
<jmorris@namei.org>
next prev parent reply other threads:[~2019-09-30 0:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-10 22:01 [GIT PULL][SECURITY] Kernel lockdown patches for v5.4 James Morris
2019-09-25 14:54 ` Jiri Kosina
2019-09-27 18:10 ` Matthew Garrett
2019-09-27 18:19 ` Linus Torvalds
2019-09-28 15:53 ` Linus Torvalds
2019-09-30 0:03 ` James Morris [this message]
2019-09-28 15:55 ` pr-tracker-bot
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.1909301002020.22854@namei.org \
--to=jmorris@namei.org \
--cc=dhowells@redhat.com \
--cc=jikos@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=mjg59@google.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;
as well as URLs for NNTP newsgroup(s).