From: Paul Mundt <lethal@linux-sh.org>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH] sh_net: Do not implement socketcall, use specific syscalls.
Date: Thu, 02 Sep 2010 02:53:56 +0000 [thread overview]
Message-ID: <20100902025356.GB10947@linux-sh.org> (raw)
In-Reply-To: <1283305771-31182-2-git-send-email-carmelo.amoroso@st.com>
On Wed, Sep 01, 2010 at 03:57:09AM +0200, Carmelo AMOROSO wrote:
> Socket syscalls entries are now available in the syscall table,
> so it does not need to implement the multipler syscall.
> It is mapped into the sys_ni_syscall.
>
I don't see how we can make this sort of change safely, it's part of the
existing ABI. Going forward we can gradually migrate people over to using
the broken out syscalls directly, but we will need to maintain
compatability with old binaries almost indefinitely.
next prev parent reply other threads:[~2010-09-02 2:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-01 1:49 [PATCH] sh_net: Do not implement socketcall, use specific syscalls Carmelo AMOROSO
2010-09-01 1:57 ` Carmelo AMOROSO
2010-09-02 2:53 ` Paul Mundt [this message]
2010-09-02 4:27 ` [PATCH] sh_net: Do not implement socketcall, use specific Carmelo AMOROSO
2010-09-02 6:14 ` [PATCH] sh_net: Do not implement socketcall, use specific syscalls Paul Mundt
2010-09-02 6:27 ` [PATCH] sh_net: Do not implement socketcall, use specific 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=20100902025356.GB10947@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;
as well as URLs for NNTP newsgroup(s).