All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Snitzer <snitzer@redhat.com>
To: James Bottomley <jbottomley@odin.com>, hare@suse.de
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"agk@redhat.com" <agk@redhat.com>, "hch@lst.de" <hch@lst.de>,
	"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
	"sfr@canb.auug.org.au" <sfr@canb.auug.org.au>,
	"jim.epost@gmail.com" <jim.epost@gmail.com>,
	"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
	"dm-devel@redhat.com" <dm-devel@redhat.com>
Subject: Re: randconfig build error with next-20150908, in drivers/md/dm-mpath.c
Date: Tue, 8 Sep 2015 14:30:22 -0400	[thread overview]
Message-ID: <20150908183021.GA3019@redhat.com> (raw)
In-Reply-To: <1441733672.5932.1.camel@Odin.com>

On Tue, Sep 08 2015 at  1:34pm -0400,
James Bottomley <jbottomley@odin.com> wrote:

> On Tue, 2015-09-08 at 13:23 -0400, Mike Snitzer wrote:
> > On Tue, Sep 08 2015 at  1:10pm -0400,
> > Jim Davis <jim.epost@gmail.com> wrote:
> > 
> > > Building with the attached random configuration file,
> > > 
> > > drivers/built-in.o: In function `activate_path':
> > > /home/jim/linux-next/drivers/md/dm-mpath.c:1225: undefined reference
> > > to `scsi_dh_activate'
> > > drivers/built-in.o: In function `parse_path':
> > > /home/jim/linux-next/drivers/md/dm-mpath.c:581: undefined reference to
> > > `scsi_dh_attached_handler_name'
> > > /home/jim/linux-next/drivers/md/dm-mpath.c:600: undefined reference to
> > > `scsi_dh_attach'
> > > /home/jim/linux-next/drivers/md/dm-mpath.c:615: undefined reference to
> > > `scsi_dh_set_params'
> > 
> > These DM-mpath changes were staged via linux-scsi.  Cc'ing James and Christoph.
> 
> [adding linux-scsi]
> 
> It must be Hannes' dm changes ... you acked them.  I take it the problem
> is now dm-mpath won't build without CONFIG_SCSI?  How do you want it
> fixed?  We can either add a Kconfig dependency or try to disentangle
> them again.

OK (Hannes' changes).  I'm fine with seeing DM_MULTIPATH depend on
CONFIG_SCSI.

The Kconfig for DM_MULTIPATH is clearly stale:

        # nasty syntax but means make DM_MULTIPATH independent
        # 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

James, if you have a vision for how to fix this please feel free.
Otherwise, Hannes, care to send a patch to fix this?

Thanks,
Mike

  reply	other threads:[~2015-09-08 18:30 UTC|newest]

Thread overview: 11+ 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 17:34     ` James Bottomley
2015-09-08 18:30     ` Mike Snitzer [this message]
2015-09-13 14:29       ` Hannes Reinecke
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
2015-09-11 18:54       ` James Bottomley

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=20150908183021.GA3019@redhat.com \
    --to=snitzer@redhat.com \
    --cc=agk@redhat.com \
    --cc=dm-devel@redhat.com \
    --cc=hare@suse.de \
    --cc=hch@lst.de \
    --cc=jbottomley@odin.com \
    --cc=jim.epost@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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.