From: Fengguang Wu <wfg@linux.intel.com>
To: "Nicholas A. Bellinger" <nab@linux-iscsi.org>
Cc: Christoph Hellwig <hch@infradead.org>,
linux-scsi@vger.kernel.org, target-devel@vger.kernel.org
Subject: Re: ERROR: "target_emulate_set_target_port_groups" [drivers/target/target_core_pscsi.ko] undefined!
Date: Wed, 13 Jun 2012 12:24:29 +0800 [thread overview]
Message-ID: <20120613042429.GB25842@localhost> (raw)
In-Reply-To: <1339560582.13709.234.camel@haakon2.linux-iscsi.org>
On Tue, Jun 12, 2012 at 09:09:42PM -0700, Nicholas A. Bellinger wrote:
> Hi Wu!
>
> On Wed, 2012-06-13 at 10:38 +0800, wfg@linux.intel.com wrote:
> > FYI, kernel build failed on
> >
> > tree: git://git.kernel.org/pub/scm/linux/kernel/git/nab/target-pending.git for-next
> > head: 414e7417f737b31a8e442214bcd6b2e9333761fd
> > commit: e6baaa4223317089ac1f35d476a42976f01fe375 [5/15] target: add a pase_cdb method to the backend drivers
> > config: i386-allmodconfig (attached as .config)
> >
> > All related error/warning messages are:
> >
> > ERROR: "target_emulate_set_target_port_groups" [drivers/target/target_core_pscsi.ko] undefined!
> > ERROR: "target_emulate_report_target_port_groups" [drivers/target/target_core_pscsi.ko] undefined!
> >
> > ---
> > 0-DAY kernel build testing backend Open Source Technology Centre
> > Fengguang Wu <wfg@linux.intel.com> Intel Corporation
>
> So the code in question ends up getting removed in the next patch:
>
> [6/15] pscsi: stop parsing most commands
>
> but as you've noticed this series is not cleanly bisectable..
Right. I'm build testing every single commit to make linux more
bisectable ;-)
> I'll go ahead and drop this problematic piece of code from patch #5 and
> respin target-pending/for-next shortly.
Great, thank you for fixing it!
Fengguang
prev parent reply other threads:[~2012-06-13 4:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-13 2:38 ERROR: "target_emulate_set_target_port_groups" [drivers/target/target_core_pscsi.ko] undefined! wfg
2012-06-13 4:09 ` Nicholas A. Bellinger
2012-06-13 4:24 ` Fengguang Wu [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=20120613042429.GB25842@localhost \
--to=wfg@linux.intel.com \
--cc=hch@infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=nab@linux-iscsi.org \
--cc=target-devel@vger.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;
as well as URLs for NNTP newsgroup(s).