[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CALxhOni=HJ=88Hw3EqG9ayuEp4xTE0HfeEj3jgF8hrFBXLh3hQ@mail.gmail.com>
Date: Tue, 6 Nov 2018 07:59:04 +0530
From: Firoz Khan <firoz.khan@...aro.org>
To: Max Filippov <jcmvbkbc@...il.com>
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 Mailman List <y2038@...ts.linaro.org>,
Linux Kernel Mailing List <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 <marcin.juszkiewicz@...aro.org>
Subject: Re: [PATCH v1 1/4] xtensa: move SYS_XTENSA_* macros to non uapi header
Hi Max,
On Tue, 6 Nov 2018 at 02:59, Max Filippov <jcmvbkbc@...il.com> wrote:
>
> On Thu, Nov 1, 2018 at 6:56 AM Firoz Khan <firoz.khan@...aro.org> wrote:
> > All the SYS_XTENSA_* macros used by sysxtensa syscall
> > handlers are resides in the uapi header file move to
> > non uapi header asm/unistd.h as it is not used by any
> > user space applications.
>
> These definitions are meant to be used by the userspace to
> perform atomic operations in the absence of atomic access
> instructions in the xtensa CPU variant.
Ohh. I can revert these changes.
Thanks for your feedback.
Firoz
>
> --
> Thanks.
> -- Max
Powered by blists - more mailing lists