SUPERH platform development
 help / color / mirror / Atom feed
From: Paul Mundt <lethal@linux-sh.org>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH] sh: Add syscall entries for non multiplexed socket calls
Date: Tue, 14 Sep 2010 08:42:37 +0000	[thread overview]
Message-ID: <20100914084237.GO7336@linux-sh.org> (raw)
In-Reply-To: <1283305771-31182-1-git-send-email-carmelo.amoroso@st.com>

On Wed, Sep 01, 2010 at 03:49:29AM +0200, Carmelo AMOROSO wrote:
> Linux kernel already has socket syscalls that can be invoked
> without the multiplexing sys_socketcall wrapper.
> C library wrappers are ready to use them directly. It needs just
> to define the missing syscall numbers and provide the related entries
> into the syscalls table, like sh64 aleady does.
> 
> Signed-off-by: Francesco Rundo <francesco.rundo@st.com>
> Signed-off-by: Carmelo Amoroso <carmelo.amoroso@st.com>

I've applied this now, with the addition of recvmmsg being wired up and
the ignore macro killed.

  reply	other threads:[~2010-09-14  8:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-01  1:49 [PATCH] sh: Add syscall entries for non multiplexed socket calls Carmelo AMOROSO
2010-09-14  8:42 ` Paul Mundt [this message]
2010-09-14  8:47 ` Carmelo AMOROSO

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=20100914084237.GO7336@linux-sh.org \
    --to=lethal@linux-sh.org \
    --cc=linux-sh@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