From: Paul Moore <paul@paul-moore.com>
To: linux-s390@vger.kernel.org
Subject: Re: [libseccomp] Re: [PATCH] arch: update s390/s390x system call tables
Date: Fri, 12 Feb 2016 16:27:11 +0000 [thread overview]
Message-ID: <1623819.nA2UEgrD8A@sifl> (raw)
In-Reply-To: <20160211121239.GB4020@osiris>
On Thursday, February 11, 2016 01:12:39 PM Heiko Carstens wrote:
> On Tue, Feb 09, 2016 at 10:55:08AM -0500, Paul Moore wrote:
> > On Tue, Nov 10, 2015 at 8:05 PM, Paul Moore <pmoore@redhat.com> wrote:
> > > On Monday, November 09, 2015 01:15:39 PM Heiko Carstens wrote:
> > >> s390 and s390x gained quite a few new system calls:
> > >> - numa related system calls
> > >> - the separated socket system calls
> > >> - two more s390 specific pci mmio system calls
> > >>
> > >> All architectures got the new membarrier and userfaultfd system calls.
> > >>
> > >> This patch updates the s390 specific system call tables and updates
> > >> other
> > >> architectures where needed.
> > >>
> > >> Also remove some extra whitespace from the s390 specific system call
> > >> tables.
> > >>
> > >> Both 'make check' and './regression -T live' still work for s390 and
> > >> s390x
> > >> after this update.
> > >
> > > Thanks for the patch, I'm still reviewing it so it's not yet merged (got
> > > tangled up in some other 4.3 related updates) but I didn't want you to
> > > think I was ignoring you.
> >
> > My apologies for taking so long - the fixes needed for 4.3 were quite
> > complex - but your patch is now merged, if you could verify that
> > everything is still working on s390/s390x that would be helpful.
>
> Hi Paul,
>
> I just verified that both s390 and s390x still pass all test cases.
That's great, thanks for your help!
--
paul moore
www.paul-moore.com
parent reply other threads:[~2016-02-12 16:27 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20160211121239.GB4020@osiris>]
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=1623819.nA2UEgrD8A@sifl \
--to=paul@paul-moore.com \
--cc=linux-s390@vger.kernel.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