linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Naman Jain <namjain@linux.microsoft.com>
To: Zhenghan Cheng <chengzhenghan@uniontech.com>,
	herbert@gondor.apana.org.au, davem@davemloft.net,
	peterz@infradead.org, acme@kernel.org, namhyung@kernel.org,
	kys@microsoft.com, haiyangz@microsoft.com, wei.liu@kernel.org,
	decui@microsoft.com, rafael@kernel.org, jgross@suse.com,
	Jason@zx2c4.com, mhiramat@kernel.org, ebiggers@kernel.org,
	masahiroy@kernel.org
Cc: linux-kernel@vger.kernel.org, mark.rutland@arm.com,
	alexander.shishkin@linux.intel.com, jolsa@kernel.org,
	irogers@google.com, adrian.hunter@intel.com,
	kan.liang@linux.intel.com, lenb@kernel.org,
	ajay.kaher@broadcom.com, alexey.makhalov@broadcom.com,
	bcm-kernel-feedback-list@broadcom.com, ppaalanen@gmail.com,
	boris.ostrovsky@oracle.com, nathan@kernel.org, nicolas@fjasle.eu,
	ilpo.jarvinen@linux.intel.com, usamaarif642@gmail.com,
	ubizjat@gmail.com, dyoung@redhat.com,
	myrrhperiwinkle@qtmlabs.xyz, guoweikang.kernel@gmail.com,
	graf@amazon.com, chao.gao@intel.com, chang.seok.bae@intel.com,
	sohil.mehta@intel.com, vigbalas@amd.com,
	aruna.ramakrishna@oracle.com, zhangkunbo@huawei.com,
	fvdl@google.com, gatlin.newhouse@gmail.com, snovitoll@gmail.com,
	bjohannesmeyer@gmail.com, glider@google.com, david@redhat.com,
	lorenzo.stoakes@oracle.com, Liam.Howlett@oracle.com,
	shivankg@amd.com, peterx@redhat.com, dan.j.williams@intel.com,
	dave.jiang@intel.com, kevin.brodsky@arm.com, willy@infradead.org,
	linux@treblig.org, Neeraj.Upadhyay@amd.com,
	wangyuli@uniontech.com, linux-crypto@vger.kernel.org,
	linux-perf-users@vger.kernel.org, linux-hyperv@vger.kernel.org,
	linux-acpi@vger.kernel.org, linux-pci@vger.kernel.org,
	linux-efi@vger.kernel.org, linux-kbuild@vger.kernel.org,
	Huacai Chen <chenhuacai@loongson.cn>,
	Zhenghan Cheng <your_email@example.com>
Subject: Re: [PATCH] x86: Fix build warnings about export.h
Date: Thu, 12 Jun 2025 15:27:55 +0530	[thread overview]
Message-ID: <42abc705-bdb5-4be0-9fe7-b49d0a0d9507@linux.microsoft.com> (raw)
In-Reply-To: <20250612093021.7187-1-chengzhenghan@uniontech.com>



On 6/12/2025 3:00 PM, Zhenghan Cheng wrote:
> After commit a934a57a42f64a4 ("scripts/misc-check:
> check missing #include <linux/export.h> when W=1")
> and commit 7d95680d64ac8e836c ("scripts/misc-check:
> check unnecessary #include <linux/export.h> when W=1"),
> we get some build warnings with W=1,such as:
> 
> arch/x86/coco/sev/core.c: warning: EXPORT_SYMBOL() is used, but #include <linux/export.h> is missing
> arch/x86/crypto/aria_aesni_avx2_glue.c: warning: EXPORT_SYMBOL() is used, but #include <linux/export.h> is missing
> arch/x86/kernel/unwind_orc.c: warning: EXPORT_SYMBOL() is used, but #include <linux/export.h> is missing
> arch/x86/kvm/hyperv.c: warning: EXPORT_SYMBOL() is used, but #include <linux/export.h> is missing
> arch/x86/events/intel/core.c: warning: EXPORT_SYMBOL() is not used, but #include <linux/export.h> is present
> arch/x86/events/zhaoxin/core.c: warning: EXPORT_SYMBOL() is not used, but #include <linux/export.h> is present
> arch/x86/kernel/crash.c: warning: EXPORT_SYMBOL() is not used, but #include <linux/export.h> is present
> arch/x86/kernel/devicetree.c: warning: EXPORT_SYMBOL() is not used, but #include <linux/export.h> is present
> 
> so fix these build warnings for x86.
> 
> Signed-off-by: "Zhenghan Cheng" <chengzhenghan@uniontech.com>
> Suggested-by: "Huacai Chen" <chenhuacai@loongson.cn>
> 


Thanks for sharing.

FYI, I sent a patch to fix these warnings in Hyper-V related drivers
here:
https://lore.kernel.org/all/20250611100459.92900-1-namjain@linux.microsoft.com/

Some of the files are common to the ones in your patch.

Regards,
Naman



      reply	other threads:[~2025-06-12  9:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-12  9:30 [PATCH] x86: Fix build warnings about export.h Zhenghan Cheng
2025-06-12  9:57 ` Naman Jain [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=42abc705-bdb5-4be0-9fe7-b49d0a0d9507@linux.microsoft.com \
    --to=namjain@linux.microsoft.com \
    --cc=Jason@zx2c4.com \
    --cc=Liam.Howlett@oracle.com \
    --cc=Neeraj.Upadhyay@amd.com \
    --cc=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=ajay.kaher@broadcom.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=alexey.makhalov@broadcom.com \
    --cc=aruna.ramakrishna@oracle.com \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=bjohannesmeyer@gmail.com \
    --cc=boris.ostrovsky@oracle.com \
    --cc=chang.seok.bae@intel.com \
    --cc=chao.gao@intel.com \
    --cc=chengzhenghan@uniontech.com \
    --cc=chenhuacai@loongson.cn \
    --cc=dan.j.williams@intel.com \
    --cc=dave.jiang@intel.com \
    --cc=davem@davemloft.net \
    --cc=david@redhat.com \
    --cc=decui@microsoft.com \
    --cc=dyoung@redhat.com \
    --cc=ebiggers@kernel.org \
    --cc=fvdl@google.com \
    --cc=gatlin.newhouse@gmail.com \
    --cc=glider@google.com \
    --cc=graf@amazon.com \
    --cc=guoweikang.kernel@gmail.com \
    --cc=haiyangz@microsoft.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=ilpo.jarvinen@linux.intel.com \
    --cc=irogers@google.com \
    --cc=jgross@suse.com \
    --cc=jolsa@kernel.org \
    --cc=kan.liang@linux.intel.com \
    --cc=kevin.brodsky@arm.com \
    --cc=kys@microsoft.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-efi@vger.kernel.org \
    --cc=linux-hyperv@vger.kernel.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=linux@treblig.org \
    --cc=lorenzo.stoakes@oracle.com \
    --cc=mark.rutland@arm.com \
    --cc=masahiroy@kernel.org \
    --cc=mhiramat@kernel.org \
    --cc=myrrhperiwinkle@qtmlabs.xyz \
    --cc=namhyung@kernel.org \
    --cc=nathan@kernel.org \
    --cc=nicolas@fjasle.eu \
    --cc=peterx@redhat.com \
    --cc=peterz@infradead.org \
    --cc=ppaalanen@gmail.com \
    --cc=rafael@kernel.org \
    --cc=shivankg@amd.com \
    --cc=snovitoll@gmail.com \
    --cc=sohil.mehta@intel.com \
    --cc=ubizjat@gmail.com \
    --cc=usamaarif642@gmail.com \
    --cc=vigbalas@amd.com \
    --cc=wangyuli@uniontech.com \
    --cc=wei.liu@kernel.org \
    --cc=willy@infradead.org \
    --cc=your_email@example.com \
    --cc=zhangkunbo@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;
as well as URLs for NNTP newsgroup(s).