From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: "K. Y. Srinivasan" <kys@microsoft.com>,
linux-kernel@vger.kernel.org, devel@linuxdriverproject.org,
ohering@suse.com, jbottomley@parallels.com, hch@infradead.org,
linux-scsi@vger.kernel.org, apw@canonical.com,
vkuznets@redhat.com, jasowang@redhat.com,
martin.petersen@oracle.com, hare@suse.de
Subject: Re: [PATCH 1/1] scsi: storvsc: Fix a build issue reported by kbuild test robot
Date: Fri, 26 Feb 2016 14:25:21 -0800 [thread overview]
Message-ID: <1456525521.2369.54.camel@HansenPartnership.com> (raw)
In-Reply-To: <1456530314-22250-1-git-send-email-kys@microsoft.com>
On Fri, 2016-02-26 at 15:45 -0800, K. Y. Srinivasan wrote:
> tree: https://na01.safelinks.protection.outlook.com/?url=https%3a%2
> f%2fgit.kernel.org%2fpub%2fscm%2flinux%2fkernel%2fgit%2ftorvalds%2fli
> nux.git&data=01%7c01%7ckys%40microsoft.com%7ce2e0622715844b79ad7108d3
> 2796ec3c%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=ubr4GbBaNS%2ftO
> z%2buJBk0CL9N0UNG9x2TidLgy6Yovg4%3d master
> head: 03c21cb775a313f1ff19be59c5d02df3e3526471
> commit: dac582417bc449b1f7f572d3f1dd9d23eec15cc9 storvsc: Properly
> support Fibre Channel devices
> date: 3 weeks ago
> config: x86_64-randconfig-s3-01281016 (attached as .config)
> reproduce:
> git checkout dac582417bc449b1f7f572d3f1dd9d23eec15cc9
> # save the attached .config to linux build tree
> make ARCH=x86_64
>
> All errors (new ones prefixed by >>):
>
> drivers/built-in.o: In function `storvsc_remove':
> > > storvsc_drv.c:(.text+0x213af7): undefined reference to
> > > `fc_remove_host'
> drivers/built-in.o: In function `storvsc_drv_init':
> > > storvsc_drv.c:(.init.text+0xcbcc): undefined reference to
> > > `fc_attach_transport'
> > > storvsc_drv.c:(.init.text+0xcc06): undefined reference to
> > > `fc_release_transport'
> drivers/built-in.o: In function `storvsc_drv_exit':
> > > storvsc_drv.c:(.exit.text+0x123c): undefined reference to
> > > `fc_release_transport'
>
> With this commit, the storvsc driver depends on FC atttributes. Make
> this
> dependency explicit.
>
> Signed-off-by: K. Y. Srinivasan <kys@microsoft.com>
> Reported-by: Fengguang Wu <fengguang.wu@intel.com>
> ---
> drivers/scsi/Kconfig | 1 +
> 1 files changed, 1 insertions(+), 0 deletions(-)
>
> diff --git a/drivers/scsi/Kconfig b/drivers/scsi/Kconfig
> index 64eed87..24365c3 100644
> --- a/drivers/scsi/Kconfig
> +++ b/drivers/scsi/Kconfig
> @@ -594,6 +594,7 @@ config XEN_SCSI_FRONTEND
> config HYPERV_STORAGE
> tristate "Microsoft Hyper-V virtual storage driver"
> depends on SCSI && HYPERV
> + depends on SCSI_FC_ATTRS
Well, I suppose continually sending the wrong patch until I get annoyed
enough to send the right one is one way of doing it. This patch is
wrong. what you want is below.
You want HYPERV_STORAGE to be built in if the FC attributes are,
otherwise you don't care because if they're N the FC code will be
compiled out.
James
---
diff --git a/drivers/scsi/Kconfig b/drivers/scsi/Kconfig
index e2f31c9..5ecabdb 100644
--- a/drivers/scsi/Kconfig
+++ b/drivers/scsi/Kconfig
@@ -596,6 +596,7 @@ config XEN_SCSI_FRONTEND
config HYPERV_STORAGE
tristate "Microsoft Hyper-V virtual storage driver"
depends on SCSI && HYPERV
+ depends on m || SCSI_FC_ATTRS
default HYPERV
help
Select this option to enable the Hyper-V virtual storage driver.
next prev parent reply other threads:[~2016-02-26 22:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-26 23:45 [PATCH 1/1] scsi: storvsc: Fix a build issue reported by kbuild test robot K. Y. Srinivasan
2016-02-26 23:45 ` K. Y. Srinivasan
2016-02-26 22:25 ` James Bottomley [this message]
2016-02-26 23:22 ` KY Srinivasan
2016-02-26 23:33 ` James Bottomley
2016-02-26 23:58 ` KY Srinivasan
-- strict thread matches above, loose matches on Subject: below --
2016-01-28 7:29 K. Y. Srinivasan
2016-01-28 7:29 ` K. Y. Srinivasan
2016-01-28 6:02 ` James Bottomley
2016-01-28 15:46 ` KY Srinivasan
2016-01-28 15:56 ` Olaf Hering
2016-01-28 19:07 ` KY Srinivasan
2016-01-28 19:22 ` James Bottomley
2016-01-28 19:28 ` KY Srinivasan
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=1456525521.2369.54.camel@HansenPartnership.com \
--to=james.bottomley@hansenpartnership.com \
--cc=apw@canonical.com \
--cc=devel@linuxdriverproject.org \
--cc=hare@suse.de \
--cc=hch@infradead.org \
--cc=jasowang@redhat.com \
--cc=jbottomley@parallels.com \
--cc=kys@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=ohering@suse.com \
--cc=vkuznets@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.