linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Firoz Khan <firoz.khan@linaro.org>
To: Max Filippov <jcmvbkbc@gmail.com>
Cc: Chris Zankel <chris@zankel.net>,
	linux-xtensa@linux-xtensa.org,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Philippe Ombredanne <pombredanne@nexb.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	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>,
	Arnd Bergmann <arnd@arndb.de>,
	Deepa Dinamani <deepa.kernel@gmail.com>,
	Marcin Juszkiewicz <marcin.juszkiewicz@linaro.org>
Subject: Re: [PATCH v2 1/3] xtensa: add __NR_syscalls along with __NR_syscall_count
Date: Fri, 16 Nov 2018 11:18:35 +0530	[thread overview]
Message-ID: <CALxhOngbgaqmcNPJ3xiBLrk35UWQ4ThJ-rApbd1z+9772yGpyQ@mail.gmail.com> (raw)
In-Reply-To: <CAMo8BfKM0M-f9UNmz0o9qZb9srJn7yxkYVYjqGc84c0eO5jnmg@mail.gmail.com>

Hi Max,

On Fri, 16 Nov 2018 at 01:15, Max Filippov <jcmvbkbc@gmail.com> wrote:
>
> On Thu, Nov 15, 2018 at 2:05 AM Firoz Khan <firoz.khan@linaro.org> wrote:
> > On Wed, 14 Nov 2018 at 05:19, Max Filippov <jcmvbkbc@gmail.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.

Great, thanks!

Firoz
>
> --
> Thanks.
> -- Max

  reply	other threads:[~2018-11-16  5:48 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-13 10:19 [PATCH v2 0/3] xtensa: system call table generation support Firoz Khan
2018-11-13 10:19 ` [PATCH v2 1/3] xtensa: add __NR_syscalls along with __NR_syscall_count Firoz Khan
2018-11-13 23:49   ` Max Filippov
2018-11-15 10:05     ` Firoz Khan
2018-11-15 19:45       ` Max Filippov
2018-11-16  5:48         ` Firoz Khan [this message]
2018-11-13 10:19 ` [PATCH v2 2/3] xtensa: add system call table generation support Firoz Khan
2018-11-13 10:19 ` [PATCH v2 3/3] xtensa: generate uapi header and syscall table header files Firoz Khan
2018-11-13 23:53 ` [PATCH v2 0/3] xtensa: system call table generation support Max Filippov
2018-11-15  9:57   ` Firoz Khan
2018-11-15 20:16     ` Max Filippov
2018-11-16  5:47       ` 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=CALxhOngbgaqmcNPJ3xiBLrk35UWQ4ThJ-rApbd1z+9772yGpyQ@mail.gmail.com \
    --to=firoz.khan@linaro.org \
    --cc=arnd@arndb.de \
    --cc=chris@zankel.net \
    --cc=deepa.kernel@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jcmvbkbc@gmail.com \
    --cc=kstewart@linuxfoundation.org \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-xtensa@linux-xtensa.org \
    --cc=marcin.juszkiewicz@linaro.org \
    --cc=pombredanne@nexb.com \
    --cc=tglx@linutronix.de \
    --cc=y2038@lists.linaro.org \
    --subject='Re: [PATCH v2 1/3] xtensa: add __NR_syscalls along with __NR_syscall_count' \
    /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

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).