All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kees Cook <keescook@chromium.org>
To: Michal Hocko <mhocko@kernel.org>
Cc: Michael Ellerman <mpe@ellerman.id.au>,
	Will Drewry <wad@chromium.org>,
	linux-s390 <linux-s390@vger.kernel.org>,
	PowerPC <linuxppc-dev@lists.ozlabs.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: samples/seccomp/ broken when cross compiling s390, ppc allyesconfig
Date: Thu, 22 Feb 2018 09:30:35 -0800	[thread overview]
Message-ID: <CAGXu5jLLDOqoSn9usuA-pRLb5X=zK6MYdUVMPEh7x7oMgnU5cQ@mail.gmail.com> (raw)
In-Reply-To: <20180222130738.GG30681@dhcp22.suse.cz>

On Thu, Feb 22, 2018 at 5:07 AM, Michal Hocko <mhocko@kernel.org> wrote:
> On Wed 14-02-18 09:14:47, Kees Cook wrote:
> [...]
>> I can send it through my seccomp tree via James Morris.
>
> Could you please do it?

Hi! Yes, sorry, this fell through the cracks. Now applied.

-Kees

-- 
Kees Cook
Pixel Security

  reply	other threads:[~2018-02-22 17:30 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-12 13:37 samples/seccomp/ broken when cross compiling s390, ppc allyesconfig Michal Hocko
2018-02-13  3:25 ` Michael Ellerman
2018-02-13  3:25   ` Michael Ellerman
2018-02-13  5:54   ` Kees Cook
2018-02-13  8:59     ` Michal Hocko
2018-02-13 10:16     ` Michael Ellerman
2018-02-13 10:32       ` Michal Hocko
2018-02-13 21:27         ` Kees Cook
2018-02-14  9:20           ` Michal Hocko
2018-02-14  9:20             ` Michal Hocko
2018-02-14 17:14             ` Kees Cook
2018-02-14 17:14               ` Kees Cook
2018-02-14 23:23               ` Michael Ellerman
2018-02-22 13:07               ` Michal Hocko
2018-02-22 17:30                 ` Kees Cook [this message]
2018-02-23  9:12                   ` Michal Hocko

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='CAGXu5jLLDOqoSn9usuA-pRLb5X=zK6MYdUVMPEh7x7oMgnU5cQ@mail.gmail.com' \
    --to=keescook@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mhocko@kernel.org \
    --cc=mpe@ellerman.id.au \
    --cc=wad@chromium.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.