From: Michael Ellerman <mpe@ellerman.id.au>
To: Purcareata Bogdan <b43198@freescale.com>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Bogdan Purcareata <bogdan.purcareata@freescale.com>,
paulus@samba.org, linuxppc-dev@lists.ozlabs.org,
linux-kernel@vger.kernel.org, pmoore@redhat.com,
strosake@linux.vnet.ibm.com, Scott Wood <scottwood@freescale.com>
Subject: Re: [PATCH v4 0/3] powerpc: Enable seccomp filter support
Date: Wed, 25 Mar 2015 20:31:37 +1100 [thread overview]
Message-ID: <1427275897.31588.2.camel@ellerman.id.au> (raw)
In-Reply-To: <550FFCAB.8080409@freescale.com>
On Mon, 2015-03-23 at 13:44 +0200, Purcareata Bogdan wrote:
> On 27.02.2015 22:54, Benjamin Herrenschmidt wrote:
> > On Fri, 2015-02-27 at 09:28 +0200, Purcareata Bogdan wrote:
> >> Ping?
> >
> > What is the ping for ?
> >
> > Ben.
>
> Hello Ben,
>
> I just wanted to check with you what's the current status of these
> patches. I noticed in patchwork [1][2][3] that the patches are marked as
> non-applicable.
>
> As of today, I cloned Michael Ellerman's tree [4], applied the patches
> on the master branch, compiled and tested. Tests pass both with the
> libseccomp regression suite and my LXC tests.
>
> Is there a specific tree I should send them against, or on another
> mailing list? Is there any other reason the patches are not applicable?
I just haven't had time to review them properly.
Because you're touching the syscall path for all powerpc platforms it needs
more scrutiny than the average patch.
It should still make 4.1, probably :)
cheers
prev parent reply other threads:[~2015-03-25 9:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-18 8:16 Bogdan Purcareata
2015-02-18 8:16 ` [PATCH v4 1/3] powerpc: Don't force ENOSYS as error on syscall fail Bogdan Purcareata
2015-02-18 8:16 ` [PATCH v4 2/3] powerpc: Relax secure computing on syscall entry trace Bogdan Purcareata
2015-02-18 8:16 ` [PATCH v4 3/3] powerpc: Enable HAVE_ARCH_SECCOMP_FILTER Bogdan Purcareata
2015-02-27 7:28 ` [PATCH v4 0/3] powerpc: Enable seccomp filter support Purcareata Bogdan
2015-02-27 20:54 ` Benjamin Herrenschmidt
2015-03-09 8:26 ` Purcareata Bogdan
2015-03-23 11:44 ` Purcareata Bogdan
2015-03-25 9:31 ` Michael Ellerman [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=1427275897.31588.2.camel@ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=b43198@freescale.com \
--cc=benh@kernel.crashing.org \
--cc=bogdan.purcareata@freescale.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=paulus@samba.org \
--cc=pmoore@redhat.com \
--cc=scottwood@freescale.com \
--cc=strosake@linux.vnet.ibm.com \
/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®