From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: linuxppc-dev <linuxppc-dev@lists.ozlabs.org>
Subject: Re: [PATCH] Wire up recvmmsg syscall
Date: Thu, 14 Jan 2010 15:21:12 +1100 [thread overview]
Message-ID: <1263442872.724.326.camel@pasglop> (raw)
In-Reply-To: <1263442293.724.324.camel@pasglop>
On Thu, 2010-01-14 at 15:11 +1100, Benjamin Herrenschmidt wrote:
> Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
> ---
> arch/powerpc/include/asm/systbl.h | 2 ++
> arch/powerpc/include/asm/unistd.h | 3 ++-
> 2 files changed, 4 insertions(+), 1 deletions(-)
>
> diff --git a/arch/powerpc/include/asm/systbl.h b/arch/powerpc/include/asm/systbl.h
> index 07d2d19..0e92c23 100644
> --- a/arch/powerpc/include/asm/systbl.h
> +++ b/arch/powerpc/include/asm/systbl.h
> @@ -326,3 +326,5 @@ SYSCALL_SPU(perf_event_open)
> COMPAT_SYS_SPU(preadv)
> COMPAT_SYS_SPU(pwritev)
> COMPAT_SYS(rt_tgsigqueueinfo)
> +COMPAT_SYS_SPU(recvmmsg)
> +
Ignore. We don't need it, it's part of socketcalls. In fact, i386
neither, it's a bug there.
Cheers,
Ben.
prev parent reply other threads:[~2010-01-14 4:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-14 4:11 [PATCH] Wire up recvmmsg syscall Benjamin Herrenschmidt
2010-01-14 4:21 ` Benjamin Herrenschmidt [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=1263442872.724.326.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=linuxppc-dev@lists.ozlabs.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).