From: Naman Jain <namjain@linux.microsoft.com>
To: kernel test robot <lkp@intel.com>,
"K . Y . Srinivasan" <kys@microsoft.com>,
Haiyang Zhang <haiyangz@microsoft.com>,
Wei Liu <wei.liu@kernel.org>, Dexuan Cui <decui@microsoft.com>
Cc: oe-kbuild-all@lists.linux.dev,
Roman Kisel <romank@linux.microsoft.com>,
Anirudh Rayabharam <anrayabh@linux.microsoft.com>,
Saurabh Sengar <ssengar@linux.microsoft.com>,
Stanislav Kinsburskii <skinsburskii@linux.microsoft.com>,
Nuno Das Neves <nunodasneves@linux.microsoft.com>,
ALOK TIWARI <alok.a.tiwari@oracle.com>,
linux-kernel@vger.kernel.org, linux-hyperv@vger.kernel.org
Subject: Re: [PATCH v4 1/2] Drivers: hv: Export some symbols for mshv_vtl
Date: Wed, 11 Jun 2025 11:19:51 +0530 [thread overview]
Message-ID: <59ff8eb7-36e9-4d11-98a1-ee94dc657f56@linux.microsoft.com> (raw)
In-Reply-To: <202506110544.q0NDMQVc-lkp@intel.com>
On 6/11/2025 3:27 AM, kernel test robot wrote:
> Closes:https://lore.kernel.org/oe-kbuild-all/202506110544.q0NDMQVc-lkp@intel.com/
I'll fix this, along with other warnings in Hyper-V drivers in next
version. Will share it shortly.
These are exposed after these recent changes:
commit 7d95680d64ac8e836c35fd56efe77eac4e9cc26b
Author: Masahiro Yamada <masahiroy@kernel.org>
Date: Sun Jun 1 22:31:30 2025 +0900
scripts/misc-check: check unnecessary #include <linux/export.h>
when W=1
commit a934a57a42f64a40705202f84144b1a29b29f910
Author: Masahiro Yamada <masahiroy@kernel.org>
Date: Sun Jun 1 22:31:29 2025 +0900
scripts/misc-check: check missing #include <linux/export.h> when W=1
Regards,
Naman
next prev parent reply other threads:[~2025-06-11 5:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-10 5:24 [PATCH v4 0/2] Drivers: hv: Introduce new driver - mshv_vtl Naman Jain
2025-06-10 5:24 ` [PATCH v4 1/2] Drivers: hv: Export some symbols for mshv_vtl Naman Jain
2025-06-10 21:57 ` kernel test robot
2025-06-11 5:49 ` Naman Jain [this message]
2025-06-10 5:24 ` [PATCH v4 2/2] Drivers: hv: Introduce mshv_vtl driver Naman Jain
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=59ff8eb7-36e9-4d11-98a1-ee94dc657f56@linux.microsoft.com \
--to=namjain@linux.microsoft.com \
--cc=alok.a.tiwari@oracle.com \
--cc=anrayabh@linux.microsoft.com \
--cc=decui@microsoft.com \
--cc=haiyangz@microsoft.com \
--cc=kys@microsoft.com \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=nunodasneves@linux.microsoft.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=romank@linux.microsoft.com \
--cc=skinsburskii@linux.microsoft.com \
--cc=ssengar@linux.microsoft.com \
--cc=wei.liu@kernel.org \
/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
all inboxes | Powered by JetHome®