[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CALxhOnhj7qUj57tLX12KmbcE5G-zDK2Qf2fTUbQ=jpmiUcr52w@mail.gmail.com>
Date: Fri, 12 Oct 2018 15:46:29 +0530
From: Firoz Khan <firoz.khan@...aro.org>
To: Arnd Bergmann <arnd@...db.de>
Cc: linux-parisc@...r.kernel.org,
"James E . J . Bottomley" <jejb@...isc-linux.org>,
Helge Deller <deller@....de>,
Thomas Gleixner <tglx@...utronix.de>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Philippe Ombredanne <pombredanne@...b.com>,
Kate Stewart <kstewart@...uxfoundation.org>,
y2038 Mailman List <y2038@...ts.linaro.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux-Arch <linux-arch@...r.kernel.org>,
Deepa Dinamani <deepa.kernel@...il.com>,
Marcin Juszkiewicz <marcin.juszkiewicz@...aro.org>
Subject: Re: [PATCH v4 5/6] parisc: wire up rseq system call
Hi Arnd,
On Fri, 12 Oct 2018 at 15:26, Arnd Bergmann <arnd@...db.de> wrote:
>
> On Fri, Oct 12, 2018 at 11:45 AM Firoz Khan <firoz.khan@...aro.org> wrote:
> >
> > Wire up rseq system call requires an architecture specific
> > implementation as it not present now.
> >
> > Signed-off-by: Firoz Khan <firoz.khan@...aro.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.
Firoz
>
> Arnd
Powered by blists - more mailing lists