From: Yinghai Lu <yinghai@kernel.org>
To: Ravi Anand <ravi.anand@qlogic.com>
Cc: James Bottomley <James.Bottomley@suse.de>,
Vikas Chaudhary <vikas.chaudhary@qlogic.com>,
Karen Higgins <karen.higgins@qlogic.com>,
Andrew Vasquez <andrew.vasquez@qlogic.com>,
linux-scsi <linux-scsi@vger.kernel.org>
Subject: Re: scsi-next fail to be compiled
Date: Tue, 27 Jul 2010 14:45:12 -0700 [thread overview]
Message-ID: <4C4F5368.9000708@kernel.org> (raw)
In-Reply-To: <5E4F49720D0BAD499EE1F01232234BA871287C962A@AVEXMB1.qlogic.org>
On 07/27/2010 01:56 PM, Ravi Anand wrote:
>
>>> On Tue, 2010-07-27 James Bottomley wrote:
>> On Tue, 2010-07-27 at 13:45 -0700, Ravi Anand wrote:
>>
>>> On Tue, 2010-07-27 James Bottomley wrote:
>>> On Tue, 2010-07-27 at 11:56 -0700, Yinghai Lu wrote:
>>> LD drivers/scsi/built-in.o
>>> drivers/scsi/qla4xxx/built-in.o: In function `qla82xx_idc_unlock':
>>> (.text+0x8814): multiple definition of `qla82xx_idc_unlock'
>>> drivers/scsi/qla2xxx/built-in.o:(.text+0x2ea14): first defined here
>>> drivers/scsi/qla2xxx/built-in.o:(.text+0x30c56): first defined here
>>> make[1]: *** [drivers/scsi/built-in.o] Error 1
>>> make: *** [drivers/scsi/] Error 2
>>
>>> This is because exactly the same functions appear in the qla2xxx/ and
>>> qla4xxx/ directories
>>
>>> Qlogic people, please get this sorted out now, otherwise I'll drop the
>>> qla4xxx update before sending to Linus
>>
>> We will try to resolve this ASAP.
>
>> Thanks
>
>> When are you planning to send it to Linus ?
>
>> Whenever he opens the merge window ... he's been making noises like it
>> will be this week.
>
>>> The best option would be to separate out the 82xx functions so that both
>>> 2xxx and 4xxx can use them. In the interim, you could add a
>>> discriminator prefix.
>>
>> We will put in discriminator prefix and repost the patches.
>
>> Just the one patch that adds the 82xx support, if possible ... that way
>> I can just swap the bad one out.
>
> Most likely yes - it will be a single 82xx patch which you can swap out.
>
so qa2xxx and qa4xxx could be used with 82xx at same time?
Yinghai
next prev parent reply other threads:[~2010-07-27 21:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4C4F2BC0.6030905@kernel.org>
2010-07-27 19:04 ` scsi-next fail to be compiled James Bottomley
2010-07-27 20:45 ` Ravi Anand
2010-07-27 20:52 ` James Bottomley
2010-07-27 20:56 ` Ravi Anand
2010-07-27 21:45 ` Yinghai Lu [this message]
2010-07-28 10:24 ` Vikas Chaudhary
2010-07-28 15:27 ` 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=4C4F5368.9000708@kernel.org \
--to=yinghai@kernel.org \
--cc=James.Bottomley@suse.de \
--cc=andrew.vasquez@qlogic.com \
--cc=karen.higgins@qlogic.com \
--cc=linux-scsi@vger.kernel.org \
--cc=ravi.anand@qlogic.com \
--cc=vikas.chaudhary@qlogic.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.