[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1e61d31a-9bf5-af79-dbc4-87d63d24b497@microchip.com>
Date: Mon, 5 Sep 2022 11:19:41 +0000
From: <Conor.Dooley@...rochip.com>
To: <heiko@...ech.de>, <paul.walmsley@...ive.com>,
<palmer@...belt.com>, <aou@...s.berkeley.edu>
CC: <guoren@...nel.org>, <apatel@...tanamicro.com>,
<atishp@...osinc.com>, <linux-riscv@...ts.infradead.org>,
<linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2 4/5] riscv: use BIT() marco for cpufeature probing
On 05/09/2022 12:10, Heiko Stuebner wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
>
> Using the appropriate BIT macro makes the code better readable.
>
> Suggested-by: Conor Dooley <conor.dooley@...rochip.com>
> Signed-off-by: Heiko Stuebner <heiko@...ech.de>
Missing the cover-letter with the changelog?
At least, I didn't get it in my inbox. Either way,
Reviewed-by: Conor Dooley <conor.dooley@...rochip.com>
> ---
> arch/riscv/kernel/cpufeature.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/arch/riscv/kernel/cpufeature.c b/arch/riscv/kernel/cpufeature.c
> index 729f7a218093..08f7445985dc 100644
> --- a/arch/riscv/kernel/cpufeature.c
> +++ b/arch/riscv/kernel/cpufeature.c
> @@ -289,10 +289,10 @@ static u32 __init_or_module cpufeature_probe(unsigned int stage)
> u32 cpu_req_feature = 0;
>
> if (cpufeature_probe_svpbmt(stage))
> - cpu_req_feature |= (1U << CPUFEATURE_SVPBMT);
> + cpu_req_feature |= BIT(CPUFEATURE_SVPBMT);
>
> if (cpufeature_probe_zicbom(stage))
> - cpu_req_feature |= (1U << CPUFEATURE_ZICBOM);
> + cpu_req_feature |= BIT(CPUFEATURE_ZICBOM);
>
> return cpu_req_feature;
> }
> --
> 2.35.1
>
Powered by blists - more mailing lists