From: Laurence Oberman <loberman@redhat.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>,
Long Li <longli@microsoft.com>
Cc: oe-kbuild-all@lists.linux.dev,
"James E.J. Bottomley" <James.Bottomley@hansenpartnership.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
linux-hyperv@vger.kernel.org, linux-scsi@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] scsi: storvsc: Support manual scans for all Hyper-V targets
Date: Tue, 04 Aug 2026 11:37:24 -0400 [thread overview]
Message-ID: <fa5e8dd1591ada95ac3e7e371852d9d68cd33cd8.camel@redhat.com> (raw)
In-Reply-To: <202608032058.OkCwuEDu-lkp@intel.com>
On Mon, 2026-08-03 at 20:45 +0800, kernel test robot wrote:
> Hi Laurence,
>
> kernel test robot noticed the following build errors:
>
> [auto build test ERROR on jejb-scsi/for-next]
> [also build test ERROR on mkp-scsi/for-next linus/master v7.2-rc6
> next-20260731]
> [If your patch is applied to the wrong git tree, kindly drop us a
> note.
> And when submitting patch, we suggest to use '--base' as documented
> in
> https://git-scm.com/docs/git-format-patch#_base_tree_information]
>
> url:
> https://github.com/intel-lab-lkp/linux/commits/Laurence-Oberman/scsi-storvsc-Support-manual-scans-for-all-Hyper-V-targets/20260803-141419
> base:
> https://git.kernel.org/pub/scm/linux/kernel/git/jejb/scsi.git for-
> next
> patch link:
> https://lore.kernel.org/r/20260723151458.872265-1-loberman%40redhat.com
> patch subject: [PATCH] scsi: storvsc: Support manual scans for all
> Hyper-V targets
> config: i386-allmodconfig
> (https://download.01.org/0day-ci/archive/20260803/202608032058.OkCwuE
> Du-lkp@intel.com/config)
> compiler: gcc-14 (Debian 14.2.0-19) 14.2.0
> reproduce (this is a W=1 build):
> (https://download.01.org/0day-ci/archive/20260803/202608032058.OkCwuE
> Du-lkp@intel.com/reproduce)
>
> If you fix the issue in a separate patch/commit (i.e. not just a new
> version of
> the same patch/commit), kindly add following tags
> > Reported-by: kernel test robot <lkp@intel.com>
> > Closes:
> > https://lore.kernel.org/oe-kbuild-all/202608032058.OkCwuEDu-lkp@intel.com/
>
> All errors (new ones prefixed by >>, old ones prefixed by <<):
>
> > > ERROR: modpost: "scsi_scan_host_selected"
> > > [drivers/scsi/hv_storvsc.ko] undefined!
>
> --
> 0-DAY CI Kernel Test Service
> https://github.com/intel/lkp-tests/wiki
>
>
> Thanks for the report. This build failure was against v1 and was
> fixed in v2 by replacing the unexported scsi_scan_host_selected()
> helper with the exported scsi_scan_target() interface.
prev parent reply other threads:[~2026-08-04 15:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-23 15:14 [PATCH] scsi: storvsc: Support manual scans for all Hyper-V targets Laurence Oberman
2026-07-23 15:30 ` sashiko-bot
2026-07-23 15:43 ` Laurence Oberman
2026-08-03 12:45 ` kernel test robot
2026-08-04 15:37 ` Laurence Oberman [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=fa5e8dd1591ada95ac3e7e371852d9d68cd33cd8.camel@redhat.com \
--to=loberman@redhat.com \
--cc=James.Bottomley@hansenpartnership.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=linux-scsi@vger.kernel.org \
--cc=lkp@intel.com \
--cc=longli@microsoft.com \
--cc=martin.petersen@oracle.com \
--cc=oe-kbuild-all@lists.linux.dev \
--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