[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200713094538.ix5g5bt6ss55kwrn@vireshk-i7>
Date: Mon, 13 Jul 2020 15:15:38 +0530
From: Viresh Kumar <viresh.kumar@...aro.org>
To: Arnd Bergmann <arnd@...db.de>
Cc: Vincent Guittot <vincent.guittot@...aro.org>,
linux-arch@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] asm-generic/sembuf: Update architecture related
information in comment
On 20-05-20, 15:53, Viresh Kumar wrote:
> The structure came originally from x86_32 but is used by most of the
> architectures now. Update the comment which says it is for x86 only.
>
> Signed-off-by: Viresh Kumar <viresh.kumar@...aro.org>
> ---
> include/uapi/asm-generic/sembuf.h | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/include/uapi/asm-generic/sembuf.h b/include/uapi/asm-generic/sembuf.h
> index 0e709bd3d730..f54e48fc91ae 100644
> --- a/include/uapi/asm-generic/sembuf.h
> +++ b/include/uapi/asm-generic/sembuf.h
> @@ -6,9 +6,9 @@
> #include <asm/ipcbuf.h>
>
> /*
> - * The semid64_ds structure for x86 architecture.
> - * Note extra padding because this structure is passed back and forth
> - * between kernel and user space.
> + * The semid64_ds structure for most architectures (though it came from x86_32
> + * originally). Note extra padding because this structure is passed back and
> + * forth between kernel and user space.
> *
> * semid64_ds was originally meant to be architecture specific, but
> * everyone just ended up making identical copies without specific
Arnd, Ping.
--
viresh
Powered by blists - more mailing lists