[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAMo8BfKM0M-f9UNmz0o9qZb9srJn7yxkYVYjqGc84c0eO5jnmg@mail.gmail.com>
Date: Thu, 15 Nov 2018 11:45:30 -0800
From: Max Filippov <jcmvbkbc@...il.com>
To: Firoz Khan <firoz.khan@...aro.org>
Cc: Chris Zankel <chris@...kel.net>, linux-xtensa@...ux-xtensa.org,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Philippe Ombredanne <pombredanne@...b.com>,
Thomas Gleixner <tglx@...utronix.de>,
Kate Stewart <kstewart@...uxfoundation.org>,
y2038@...ts.linaro.org, LKML <linux-kernel@...r.kernel.org>,
Linux-Arch <linux-arch@...r.kernel.org>,
Arnd Bergmann <arnd@...db.de>,
Deepa Dinamani <deepa.kernel@...il.com>,
marcin.juszkiewicz@...aro.org
Subject: Re: [PATCH v2 1/3] xtensa: add __NR_syscalls along with __NR_syscall_count
On Thu, Nov 15, 2018 at 2:05 AM Firoz Khan <firoz.khan@...aro.org> wrote:
> On Wed, 14 Nov 2018 at 05:19, Max Filippov <jcmvbkbc@...il.com> wrote:
> > If we remove __NR_syscall_count from the uapi header I'd
> > suggest dropping it completely and switching its two current
> > users to __NR_syscalls.
>
> I'm not removing the __NR_syscall_count macro; just place it
> in asm/unistd.h file for the above reason.
Ok, I'll apply this series to the xtensa tree and make my cleanups
on top of it.
> FYI, I made sure that the kernel will build with my patch. I would
> appreciate if you can perform the boot test on the actual platform.
I did a simple boot testing on a range of configurations, it works.
I'll also run LTP a bit later.
--
Thanks.
-- Max
Powered by blists - more mailing lists