From: Ingo Molnar <mingo@kernel.org>
To: Kees Cook <keescook@chromium.org>
Cc: James Morris <jmorris@namei.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-security-module <linux-security-module@vger.kernel.org>,
Ingo Molnar <mingo@elte.hu>, LKML <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Borislav Petkov <bp@alien8.de>
Subject: Re: [GIT PULL] seccomp: build fix for v5.0-rc2
Date: Wed, 9 Jan 2019 07:59:16 +0100 [thread overview]
Message-ID: <20190109065916.GA29753@gmail.com> (raw)
In-Reply-To: <CAGXu5j+wvi9t-oHf4cX999aYWMhmTJ1zA1mKuNQEB_n5ixiC5w@mail.gmail.com>
* Kees Cook <keescook@chromium.org> wrote:
> This was already picked up by x86-urgent...
>
> -Kees
I'm fine with both routes - if Linus pulls this I'll zap the x86/urgent
one.
Thanks,
Ingo
next prev parent reply other threads:[~2019-01-09 6:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-08 21:04 [GIT PULL] seccomp: build fix for v5.0-rc2 James Morris
2019-01-08 21:11 ` Kees Cook
2019-01-09 6:59 ` Ingo Molnar [this message]
2019-01-10 3:18 ` Tycho Andersen
2019-01-11 7:09 ` Ingo Molnar
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=20190109065916.GA29753@gmail.com \
--to=mingo@kernel.org \
--cc=bp@alien8.de \
--cc=jmorris@namei.org \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--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).