From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Pranith Kumar <bobby.prani@gmail.com>
Cc: open list <linux-kernel@vger.kernel.org>,
Fabian Frederick <fabf@skynet.be>,
Paul Mackerras <paulus@samba.org>,
Anton Blanchard <anton@samba.org>,
Andrew Morton <akpm@linux-foundation.org>,
"open list:LINUX FOR POWERPC..." <linuxppc-dev@lists.ozlabs.org>
Subject: Re: [RFC PATCH] powerpc: Wire up three syscalls
Date: Sun, 31 Aug 2014 10:53:28 +0200 [thread overview]
Message-ID: <CAMuHMdV_naTfQOLwOshWq1Q15kSE39a8GWChsjt3RrWRcd6peg@mail.gmail.com> (raw)
In-Reply-To: <1409369788-22563-1-git-send-email-bobby.prani@gmail.com>
Hi Pranith,
On Sat, Aug 30, 2014 at 5:36 AM, Pranith Kumar <bobby.prani@gmail.com> wrote:
> I see that the three syscalls seccomp, getrandom and memfd_create are not wired
> because of which we get a warning while compilation.
>
> So I wired them up in this patch. What else needs to be done? I tried the
> memfd_test after compiling this kernel, but it is failing. What am I missing for
> this to work? Any advice is really appreciated! :)
Did it fail due to the (silly) "ifeq ($(ARCH),X86)" checks in
tools/testing/selftests/memfd/Makefile?
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next prev parent reply other threads:[~2014-08-31 8:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-30 3:36 [RFC PATCH] powerpc: Wire up three syscalls Pranith Kumar
2014-08-31 8:53 ` Geert Uytterhoeven [this message]
2014-08-31 12:52 ` Pranith Kumar
2014-08-31 14:14 ` Geert Uytterhoeven
2014-08-31 14:34 ` David Herrmann
2014-08-31 17:51 ` Pranith Kumar
2014-09-01 11:33 ` David Herrmann
2014-09-01 15:21 ` Pranith Kumar
2014-09-01 15:31 ` David Herrmann
2014-09-01 17:16 ` Pranith Kumar
2014-09-01 17:28 ` David Herrmann
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=CAMuHMdV_naTfQOLwOshWq1Q15kSE39a8GWChsjt3RrWRcd6peg@mail.gmail.com \
--to=geert@linux-m68k.org \
--cc=akpm@linux-foundation.org \
--cc=anton@samba.org \
--cc=bobby.prani@gmail.com \
--cc=fabf@skynet.be \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=paulus@samba.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).