From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: kbuild test robot <lkp@intel.com>
Cc: kbuild-all@01.org, linux-scsi@vger.kernel.org
Subject: Re: [PATCH 3/3] ses: fix discovery of SATA devices in SAS enclosures
Date: Wed, 09 Dec 2015 12:52:50 -0800 [thread overview]
Message-ID: <1449694370.2226.43.camel@HansenPartnership.com> (raw)
In-Reply-To: <201512100407.NtBT5c6i%fengguang.wu@intel.com>
On Thu, 2015-12-10 at 04:38 +0800, kbuild test robot wrote:
> Hi James,
>
> [auto build test ERROR on v4.4-rc4]
> [cannot apply to scsi/for-next next-20151209]
>
> url: https://github.com/0day-ci/linux/commits/James-Bottomley/Fix-the-problem-of-SATA-devices-within-SAS-enclosures/20151210-031802
> config: i386-randconfig-b0-12100330 (attached as .config)
> reproduce:
> # save the attached .config to linux build tree
> make ARCH=i386
>
> All errors (new ones prefixed by >>):
>
> drivers/built-in.o: In function `ses_match_to_enclosure':
> >> ses.c:(.text+0x1c04ad): undefined reference to `is_sas_attached'
> >> ses.c:(.text+0x1c0519): undefined reference to `sas_get_address'
Oh, that's the perennial file built in but dependencies are modules
problem. The fix is to add this line to the Kconfig for SCSI_ENCLOSURE
depends on m || SCSI_SAS_ATTRS != m
I'll post a v2 with that added.
James
next prev parent reply other threads:[~2015-12-09 20:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-09 19:10 [PATCH 0/3] Fix the problem of SATA devices within SAS enclosures James Bottomley
2015-12-09 19:12 ` [PATCH 1/3] scsi_transport_sas: add is_sas_attached() function James Bottomley
2015-12-15 10:16 ` Hannes Reinecke
2015-12-09 19:13 ` [PATCH 2/3] scsi_transport_sas: add function to get SAS endpoint address James Bottomley
2015-12-15 10:17 ` Hannes Reinecke
2015-12-09 19:14 ` [PATCH 3/3] ses: fix discovery of SATA devices in SAS enclosures James Bottomley
2015-12-09 20:38 ` kbuild test robot
2015-12-09 20:52 ` James Bottomley [this message]
2015-12-09 20:56 ` [PATCH v2 " James Bottomley
2015-12-15 10:17 ` Hannes Reinecke
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=1449694370.2226.43.camel@HansenPartnership.com \
--to=james.bottomley@hansenpartnership.com \
--cc=kbuild-all@01.org \
--cc=linux-scsi@vger.kernel.org \
--cc=lkp@intel.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.