[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZIykXq2U5XVZ4aB+@casper.infradead.org>
Date: Fri, 16 Jun 2023 19:05:18 +0100
From: Matthew Wilcox <willy@...radead.org>
To: Jordy Zomer <jordyzomer@...gle.com>
Cc: linux-kernel@...r.kernel.org, linux-doc@...r.kernel.org,
corbet@....net, dave.hansen@...ux.intel.com, daniel@...earbox.net,
tglx@...utronix.de, rdunlap@...radead.org,
pawan.kumar.gupta@...ux.intel.com
Subject: Re: [PATCH 1/1] nospec: Add documentation for array_index_nospec
On Fri, Jun 16, 2023 at 01:37:35PM +0000, Jordy Zomer wrote:
> +Please note that this function should only be used if the upper
> +boundary is a built-time constant, otherwise this could be
> +speculated on as well. If this is not the case please refer to
> +barrier_nospec().
"build time", not "built time". Also, "Please note that" doesn't
really add any value. You can just write:
This function should only be used if the upper boundary is a build-time
constant, otherwise this could be speculated on as well. If it is not
a constant, use barrier_nospec() instead.
Powered by blists - more mailing lists