From: Herbert Xu <herbert@gondor.apana.org.au>
To: Gonglei <arei.gonglei@huawei.com>
Cc: linux-crypto@vger.kernel.org, mst@redhat.com,
virtualization@lists.linux-foundation.org,
linux-kernel@vger.kernel.org, lixiao91@huawei.com,
wangyangxin <wangyangxin1@huawei.com>
Subject: Re: [PATCH 2/2] crypto: virtio-crypto: Fix gcc check warnings
Date: Fri, 22 Dec 2023 11:33:54 +0800 [thread overview]
Message-ID: <ZYUDop1Cv1ddrqQf@gondor.apana.org.au> (raw)
In-Reply-To: <1702294936-61080-3-git-send-email-arei.gonglei@huawei.com>
On Mon, Dec 11, 2023 at 07:42:16PM +0800, Gonglei wrote:
>
> static inline int virtio_crypto_get_current_node(void)
> {
> - int cpu, node;
> + int node;
>
> - cpu = get_cpu();
> - node = topology_physical_package_id(cpu);
> + node = topology_physical_package_id(get_cpu());
This looks like a bogus warning. I think we should do something
like this instead:
diff --git a/arch/x86/include/asm/processor.h b/arch/x86/include/asm/processor.h
index ae81a7191c1c..0cb43986061b 100644
--- a/arch/x86/include/asm/processor.h
+++ b/arch/x86/include/asm/processor.h
@@ -191,7 +191,7 @@ DECLARE_PER_CPU_READ_MOSTLY(struct cpuinfo_x86, cpu_info);
#define cpu_data(cpu) per_cpu(cpu_info, cpu)
#else
#define cpu_info boot_cpu_data
-#define cpu_data(cpu) boot_cpu_data
+#define cpu_data(cpu) ((void)cpu, boot_cpu_data)
#endif
extern const struct seq_operations cpuinfo_op;
Please send this patch to the x86 people.
Thanks,
--
Email: Herbert Xu <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
prev parent reply other threads:[~2023-12-22 3:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-11 11:42 [PATCH 0/2] crypto: virtio-crypto: Wait for tasklet to complete on device remove and fix warnings Gonglei
2023-12-11 11:42 ` [PATCH 1/2] crypto: virtio-crypto: Wait for tasklet to complete on device remove Gonglei
2023-12-22 4:35 ` Herbert Xu
2023-12-11 11:42 ` [PATCH 2/2] crypto: virtio-crypto: Fix gcc check warnings Gonglei
2023-12-22 3:33 ` Herbert Xu [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZYUDop1Cv1ddrqQf@gondor.apana.org.au \
--to=herbert@gondor.apana.org.au \
--cc=arei.gonglei@huawei.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lixiao91@huawei.com \
--cc=mst@redhat.com \
--cc=virtualization@lists.linux-foundation.org \
--cc=wangyangxin1@huawei.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox