From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm: wire up userfaultfd and membarrier syscalls
Date: Tue, 22 Sep 2015 11:47:55 +0100 [thread overview]
Message-ID: <20150922104755.GW21084@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <56013154.1010401@arm.com>
On Tue, Sep 22, 2015 at 11:45:40AM +0100, Andre Przywara wrote:
> Hi Russell,
>
> On 21/09/15 18:17, Russell King - ARM Linux wrote:
> > On Mon, Sep 21, 2015 at 06:00:33PM +0100, Andre Przywara wrote:
> >> Add the syscall numbers to the ARM syscall table. Both have
> >> been briefly tested using the provided selftests from the tools
> >> directory.
> >>
> >> Signed-off-by: Andre Przywara <andre.przywara@arm.com>
> >> ---
> >> Hi Russell,
> >>
> >> I saw that Thierry sent something similar beginning of August already
> >> (which is now outdated), is there any issue with enabling syscalls?
> >
> > The only issue there is is that this was mentioned last week, and I
> > replied about it last week.
>
> I missed that because I only looked in the ARM kernel ML, sorry about that.
>
> > I already have a patch pending for it, but I've been unable to merge
> > it into mainline as my tree became somewhat messy due to the fixes
> > missing -rc1 - which meant that my fixes branch was not recent enough
> > to take that patch. Now that those fixes are in, I can now start
> > sorting my tree out, as I'd normally do after -rc1.
>
> Fair enough and sorry for the noise.
It should be in tonights linux-next.
--
FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up
according to speedtest.net.
prev parent reply other threads:[~2015-09-22 10:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-21 17:00 [PATCH] arm: wire up userfaultfd and membarrier syscalls Andre Przywara
2015-09-21 17:17 ` Russell King - ARM Linux
2015-09-22 10:45 ` Andre Przywara
2015-09-22 10:47 ` Russell King - ARM Linux [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=20150922104755.GW21084@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=linux-arm-kernel@lists.infradead.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).