From: Carmelo AMOROSO <carmelo.amoroso@st.com>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH (sh-2.6)] sh: do not export syscalls that are actually
Date: Mon, 12 Dec 2011 10:58:39 +0000 [thread overview]
Message-ID: <4EE5DE5F.10206@st.com> (raw)
In-Reply-To: <1322685809-15587-1-git-send-email-carmelo.amoroso@st.com>
On 30/11/2011 21.56, Mike Frysinger wrote:
> On Wednesday 30 November 2011 15:43:29 Carmelo AMOROSO wrote:
>> Avoid user space to erroneously assume that a syscall is
>> implemented by picking __NR_xxx from kernel headers that are
>> actually mapped to sys_ni_syscall.
>
> Acked-by: Mike Frysinger <vapier@gentoo.org> -mike
Paul,
anu chance to include it ? to avoid any doubts, patch was done against
HEAD, the subject sh-2.6 was due to a old git setting.
cheers,
carmelo
next prev parent reply other threads:[~2011-12-12 10:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-30 20:43 [PATCH (sh-2.6)] sh: do not export syscalls that are actually not implemented Carmelo AMOROSO
2011-11-30 20:56 ` Mike Frysinger
2011-12-12 10:58 ` Carmelo AMOROSO [this message]
2011-12-13 2:22 ` Paul Mundt
2011-12-22 16:11 ` [PATCH (sh-2.6)] sh: do not export syscalls that are actually Carmelo AMOROSO
2012-03-19 13:28 ` [PATCH (sh-2.6)] sh: do not export syscalls that are actually not implemented Carmelo AMOROSO
2012-03-28 7:30 ` Paul Mundt
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=4EE5DE5F.10206@st.com \
--to=carmelo.amoroso@st.com \
--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).