From: Arnd Bergmann <arnd@arndb.de>
To: Firoz Khan <firoz.khan@linaro.org>
Cc: Parisc List <linux-parisc@vger.kernel.org>,
"James E.J. Bottomley" <jejb@parisc-linux.org>,
Helge Deller <deller@gmx.de>,
Thomas Gleixner <tglx@linutronix.de>,
gregkh <gregkh@linuxfoundation.org>,
Philippe Ombredanne <pombredanne@nexb.com>,
Kate Stewart <kstewart@linuxfoundation.org>,
y2038 Mailman List <y2038@lists.linaro.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-arch <linux-arch@vger.kernel.org>,
Deepa Dinamani <deepa.kernel@gmail.com>,
Marcin Juszkiewicz <marcin.juszkiewicz@linaro.org>
Subject: Re: [PATCH v4 5/6] parisc: wire up rseq system call
Date: Fri, 12 Oct 2018 13:52:15 +0200 [thread overview]
Message-ID: <CAK8P3a3BjuLQh0hTPFTDTkipXXQ+j8ADqbWmNpimkMDzoORkRA@mail.gmail.com> (raw)
In-Reply-To: <CALxhOnhj7qUj57tLX12KmbcE5G-zDK2Qf2fTUbQ=jpmiUcr52w@mail.gmail.com>
On Fri, Oct 12, 2018 at 12:16 PM Firoz Khan <firoz.khan@linaro.org> wrote:
>
> Hi Arnd,
>
> On Fri, 12 Oct 2018 at 15:26, Arnd Bergmann <arnd@arndb.de> wrote:
> >
> > On Fri, Oct 12, 2018 at 11:45 AM Firoz Khan <firoz.khan@linaro.org> wrote:
> > >
> > > Wire up rseq system call requires an architecture specific
> > > implementation as it not present now.
> > >
> > > Signed-off-by: Firoz Khan <firoz.khan@linaro.org>
> >
> > Didn't we conclude that this should be skipped?
>
> Helge told "I prefer to keep the warning for rseq for now.
> It reminds me that we still may want the rseq syscall.
> If the warning is a problem, you may simply add the __IGNORE_rseq define."
>
> I chose this option; I feel it looks clean
> "# rseq requires an architecture specific implementation" in syscall.tbl
> hopefully remind him to add rseq syscall implementation in this architecture.
>
But he said he wants the warning instead.
Arnd
next prev parent reply other threads:[~2018-10-12 11:52 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-12 9:43 [PATCH v4 0/6] parisc: system call table generation support Firoz Khan
2018-10-12 9:43 ` Firoz Khan
2018-10-12 9:43 ` [PATCH v4 1/6] parisc: move __IGNORE* entries to non uapi header Firoz Khan
2018-10-12 9:43 ` Firoz Khan
2018-10-12 9:43 ` [PATCH v4 2/6] parisc: add __NR_Linux_syscalls along with __NR_syscalls Firoz Khan
2018-10-12 9:43 ` Firoz Khan
2018-10-12 9:43 ` [PATCH v4 3/6] parisc: add system call table generation support Firoz Khan
2018-10-12 9:43 ` Firoz Khan
2018-10-12 10:18 ` Firoz Khan
2018-10-12 10:18 ` Firoz Khan
2018-10-12 11:51 ` Arnd Bergmann
2018-10-12 11:51 ` Arnd Bergmann
2018-10-13 15:34 ` Firoz Khan
2018-10-13 15:34 ` Firoz Khan
2018-10-12 12:07 ` Rolf Eike Beer
2018-10-12 12:07 ` Rolf Eike Beer
2018-10-12 13:57 ` Firoz Khan
2018-10-12 13:57 ` Firoz Khan
2018-10-12 14:03 ` Rolf Eike Beer
2018-10-12 14:03 ` Rolf Eike Beer
2018-10-15 4:48 ` Firoz Khan
2018-10-15 4:48 ` Firoz Khan
2018-10-15 5:16 ` Rolf Eike Beer
2018-10-15 5:16 ` Rolf Eike Beer
2018-10-15 5:45 ` Firoz Khan
2018-10-15 5:45 ` Firoz Khan
2018-10-14 1:06 ` Eugene Syromiatnikov
2018-10-14 1:06 ` Eugene Syromiatnikov
2018-10-15 5:12 ` Firoz Khan
2018-10-15 5:12 ` Firoz Khan
2018-10-12 9:44 ` [PATCH v4 4/6] parisc: uapi header and system call table file generation Firoz Khan
2018-10-12 9:44 ` Firoz Khan
2018-10-12 9:44 ` [PATCH v4 5/6] parisc: wire up rseq system call Firoz Khan
2018-10-12 9:44 ` Firoz Khan
2018-10-12 9:56 ` Arnd Bergmann
2018-10-12 9:56 ` Arnd Bergmann
2018-10-12 10:16 ` Firoz Khan
2018-10-12 10:16 ` Firoz Khan
2018-10-12 11:52 ` Arnd Bergmann [this message]
2018-10-12 11:52 ` Arnd Bergmann
2018-10-12 20:23 ` Helge Deller
2018-10-12 20:23 ` Helge Deller
2018-10-13 5:42 ` Firoz Khan
2018-10-13 5:42 ` Firoz Khan
2018-10-12 9:44 ` [PATCH v4 6/6] parisc: syscalls: Ignore nfsservctl for other architectures Firoz Khan
2018-10-12 9:44 ` Firoz Khan
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=CAK8P3a3BjuLQh0hTPFTDTkipXXQ+j8ADqbWmNpimkMDzoORkRA@mail.gmail.com \
--to=arnd@arndb.de \
--cc=deepa.kernel@gmail.com \
--cc=deller@gmx.de \
--cc=firoz.khan@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=jejb@parisc-linux.org \
--cc=kstewart@linuxfoundation.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-parisc@vger.kernel.org \
--cc=marcin.juszkiewicz@linaro.org \
--cc=pombredanne@nexb.com \
--cc=tglx@linutronix.de \
--cc=y2038@lists.linaro.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).