[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Yf/V3dlRIDxS9hWu@hirez.programming.kicks-ass.net>
Date: Sun, 6 Feb 2022 15:06:21 +0100
From: Peter Zijlstra <peterz@...radead.org>
To: Mark Rutland <mark.rutland@....com>
Cc: Boqun Feng <boqun.feng@...il.com>, linux-kernel@...r.kernel.org,
ardb@...nel.org, arnd@...db.de, will@...nel.org
Subject: Re: [PATCH v2] atomics: fix atomic64_{read_acquire,set_release}
fallbacks
On Fri, Feb 04, 2022 at 11:16:02AM +0000, Mark Rutland wrote:
> Sure; how about I add the following to the commit message:
>
> | Since the fallback templates are used to generate the atomic64_*() and
> | atomic_*() operations, the __native_word() check is added to both. For
> | the atomic_*() operations, which are always 32-bit, the __native_word()
> | check is redundant but not harmful, as it is always true.
Thanks!
Powered by blists - more mailing lists