From: James Bottomley <jbottomley@odin.com>
To: "hch@lst.de" <hch@lst.de>
Cc: "sfr@canb.auug.org.au" <sfr@canb.auug.org.au>,
"jim.epost@gmail.com" <jim.epost@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"agk@redhat.com" <agk@redhat.com>,
"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
"snitzer@redhat.com" <snitzer@redhat.com>,
"dm-devel@redhat.com" <dm-devel@redhat.com>
Subject: Re: randconfig build error with next-20150908, in drivers/md/dm-mpath.c
Date: Fri, 11 Sep 2015 18:54:01 +0000 [thread overview]
Message-ID: <1441997640.7836.1.camel@Odin.com> (raw)
In-Reply-To: <20150909160418.GB28608@lst.de>
On Wed, 2015-09-09 at 18:04 +0200, Christoph Hellwig wrote:
> Does this fix the issue for you? My Kconfig-fu isn't the best,
> but the idea behind this is that dm-mpath will depend on SCSI
> if SCSI_DH is set. If SCSI_DH is not set it will use the stubs
> and not care about SCSI.
I assume I'm OK to add
Signed-off-by: Christoph Hellwig <hch@lst.de>
(I'll assume so if you don't reply)
James
> diff --git a/drivers/md/Kconfig b/drivers/md/Kconfig
> index b597273..e9ea681 100644
> --- a/drivers/md/Kconfig
> +++ b/drivers/md/Kconfig
> @@ -393,7 +393,7 @@ config DM_MULTIPATH
> # of SCSI_DH if the latter isn't defined but if
> # it is, DM_MULTIPATH must depend on it. We get a build
> # error if SCSI_DH=m and DM_MULTIPATH=y
> - depends on SCSI_DH || !SCSI_DH
> + depends on !SCSI_DH || SCSI
> ---help---
> Allow volume managers to support multipath hardware.
>
prev parent reply other threads:[~2015-09-11 18:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-08 17:10 randconfig build error with next-20150908, in drivers/md/dm-mpath.c Jim Davis
2015-09-08 17:23 ` Mike Snitzer
2015-09-08 17:34 ` James Bottomley
2015-09-08 18:30 ` Mike Snitzer
2015-09-13 14:29 ` Hannes Reinecke
2015-09-09 16:04 ` Christoph Hellwig
2015-09-11 18:29 ` Mike Snitzer
2015-09-11 18:54 ` James Bottomley [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=1441997640.7836.1.camel@Odin.com \
--to=jbottomley@odin.com \
--cc=agk@redhat.com \
--cc=dm-devel@redhat.com \
--cc=hch@lst.de \
--cc=jim.epost@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=snitzer@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 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).