From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Arnaldo Carvalho de Melo <acme@redhat.com>,
Arnd Bergmann <arnd@arndb.de>
Cc: linux-arch@vger.kernel.org, linux-kernel@vger.kernel.org,
Linux/m68k <linux-m68k@vger.kernel.org>
Subject: sys_recvmmsg: wire up or not?
Date: Sat, 26 Dec 2009 11:39:27 +0100 [thread overview]
Message-ID: <10f740e80912260239n17bbbd08w6c3065c12bde9c95@mail.gmail.com> (raw)
On m68k, I get:
<stdin>:1523:2: warning: #warning syscall recvmmsg not implemented
so I started to wire up sys_recvmmsg.
Then I noticed it's already accessible, through sys_socketcall, as m68k defines
__ARCH_WANT_SYS_SOCKETCALL. So I guess this is a false positive?
Surprisingly, several architectures have both defined __ARCH_WANT_SYS_SOCKETCALL
and wired up sys_recvmmsg. Is this intentional?
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 reply other threads:[~2009-12-26 10:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-26 10:39 Geert Uytterhoeven [this message]
2009-12-26 11:12 ` sys_recvmmsg: wire up or not? Arnd Bergmann
2010-01-14 4:20 ` Benjamin Herrenschmidt
2010-01-14 4:20 ` Benjamin Herrenschmidt
2010-01-14 4:28 ` David Miller
2010-01-14 6:59 ` Benjamin Herrenschmidt
2010-01-14 9:33 ` Russell King
2010-01-15 3:32 ` Benjamin Herrenschmidt
2010-01-19 7:21 ` Paul Mundt
2010-01-19 7:21 ` Paul Mundt
2010-01-19 23:14 ` Benjamin Herrenschmidt
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=10f740e80912260239n17bbbd08w6c3065c12bde9c95@mail.gmail.com \
--to=geert@linux-m68k.org \
--cc=acme@redhat.com \
--cc=arnd@arndb.de \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@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;
as well as URLs for NNTP newsgroup(s).