From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, Eric Moore <eric.moore@lsi.com>,
peter Bogdanovic <pbog@us.ibm.com>,
linux-scsi <linux-scsi@vger.kernel.org>
Subject: Re: linux-next: scsi tree build failure
Date: Mon, 16 Mar 2009 08:22:22 -0500 [thread overview]
Message-ID: <1237209742.3257.33.camel@localhost.localdomain> (raw)
In-Reply-To: <20090316213945.e33f3427.sfr@canb.auug.org.au>
On Mon, 2009-03-16 at 21:39 +1100, Stephen Rothwell wrote:
> Hi James,
>
> Today's linux-next build (powerpc allyesconfig) failed like this:
>
> drivers/message/built-in.o:(.data.rel+0x88): multiple definition of `ioc_list'
> drivers/scsi/built-in.o:(.data.rel+0x2760): first defined here
>
> Caused by commit 635374e7eb110e80d9918b8611198edd56a32975 ("[SCSI]
> mpt2sas v00.100.11.15"). ioc_list is not a good choice for a global
> name. The other definition is in drivers/message/fusion/mptbase.c.
>
> I have reverted that commit for today.
Eric,
Vould we get this one sorted out before the merge window opens? ... the
simple fix seems to be to rename ioc_list in mpt2sas ... and track down
any more global symbols with unfortunate names.
James
next prev parent reply other threads:[~2009-03-16 13:22 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-16 10:39 linux-next: scsi tree build failure Stephen Rothwell
2009-03-16 13:22 ` James Bottomley [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-06-15 2:17 Stephen Rothwell
2009-06-15 15:11 ` James Bottomley
2009-06-15 21:40 ` Benjamin Herrenschmidt
2009-06-16 2:24 ` James Bottomley
2009-04-02 5:49 Stephen Rothwell
2009-04-02 14:22 ` James Bottomley
2009-04-02 17:19 ` Robert Love
2009-04-02 18:23 ` James Bottomley
2009-04-03 0:26 ` Stephen Rothwell
2009-04-03 1:16 ` James Bottomley
2009-04-03 2:37 ` Stephen Rothwell
2008-12-30 16:16 Stephen Rothwell
2008-12-30 16:30 ` James Bottomley
2008-12-15 14:37 Stephen Rothwell
2008-12-15 14:52 ` James Bottomley
2008-12-17 12:20 ` Stephen Rothwell
2008-12-21 3:30 ` Stephen Rothwell
2008-12-22 1:59 ` James Bottomley
2008-12-22 2:38 ` Stephen Rothwell
2008-10-15 6:49 Stephen Rothwell
2008-10-15 12:27 ` James Bottomley
2008-07-07 12:25 Stephen Rothwell
2008-07-07 12:25 ` Stephen Rothwell
2008-07-07 14:39 ` James Bottomley
2008-07-07 14:39 ` James Bottomley
2008-07-07 14:53 ` Robert Jennings
2008-07-07 14:53 ` Robert Jennings
2008-07-07 22:05 ` Benjamin Herrenschmidt
2008-07-07 22:05 ` Benjamin Herrenschmidt
2008-07-07 22:07 ` James Bottomley
2008-07-07 22:07 ` James Bottomley
2008-07-07 22:48 ` Benjamin Herrenschmidt
2008-07-07 22:48 ` Benjamin Herrenschmidt
2008-07-07 22:00 ` Benjamin Herrenschmidt
2008-07-07 22:00 ` Benjamin Herrenschmidt
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=1237209742.3257.33.camel@localhost.localdomain \
--to=james.bottomley@hansenpartnership.com \
--cc=eric.moore@lsi.com \
--cc=linux-next@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=pbog@us.ibm.com \
--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.