From: Jes Sorensen <jes@wildopensource.com>
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: Andrew Vasquez <andrew.vasquez@qlogic.com>,
Adrian Bunk <bunk@stusta.de>, Andrew Morton <akpm@osdl.org>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.9-rc3-mm3: `risc_code_addr01' multiple definition
Date: 21 Oct 2004 09:02:07 -0400 [thread overview]
Message-ID: <yq08ya0rzqo.fsf@jaguar.mkp.net> (raw)
In-Reply-To: <1097171420.1718.332.camel@mulgrave>
>>>>> "James" == James Bottomley <James.Bottomley@SteelEye.com> writes:
James> On Thu, 2004-10-07 at 12:29, Andrew Vasquez wrote:
>> Hmm, seems the additional 1040 support in qla1280.c is causing name
>> clashes with the firmware image in qlogicfc_asm.c. Try out the
>> attached patch (not tested) which provides the 1040 firmware image
>> unique variable names.
>>
>> Looks like there would be some name clashes in qlogicfc and
>> qlogicisp.
James> Is there any reason for these firmware image pointers not to be
James> static? At least for these drivers which are single files.
I was just thinking the same thing - 2 weeks after everybody else ;-)
You won't see me complaining about a patch doing this for the qla1280
driver.
Cheers,
Jes
next prev parent reply other threads:[~2004-10-21 13:09 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-07 8:51 2.6.9-rc3-mm3 Andrew Morton
2004-10-07 9:30 ` 2.6.9-rc3-mm3 Martin Zwickel
2004-10-07 9:41 ` 2.6.9-rc3-mm3 Nick Sanders
2004-10-07 9:50 ` 2.6.9-rc3-mm3 Andrew Morton
2004-10-07 10:10 ` 2.6.9-rc3-mm3 Martin Zwickel
2004-10-07 10:44 ` 2.6.9-rc3-mm3 Hanno Meyer-Thurow
[not found] ` <20041007125610.0019eb3d@mango.fruits.de>
2004-10-07 10:58 ` 2.6.9-rc3-mm3 Hanno Meyer-Thurow
2004-10-07 10:16 ` 2.6.9-rc3-mm3 Nick Sanders
2004-10-07 11:40 ` 2.6.9-rc3-mm3 William Lee Irwin III
2004-10-07 21:25 ` 2.6.9-rc3-mm3 J.A. Magallon
2004-10-07 21:46 ` 2.6.9-rc3-mm3 J.A. Magallon
2004-10-07 22:07 ` 2.6.9-rc3-mm3 Andrew Morton
2004-10-07 22:41 ` 2.6.9-rc3-mm3 J.A. Magallon
2004-10-07 22:54 ` 2.6.9-rc3-mm3 Andrew Morton
2004-10-07 23:06 ` 2.6.9-rc3-mm3 J.A. Magallon
2004-10-07 23:40 ` 2.6.9-rc3-mm3 Greg KH
2004-10-08 1:05 ` 2.6.9-rc3-mm3 Paul Fulghum
2004-10-08 11:23 ` 2.6.9-rc3-mm3 William Lee Irwin III
2004-10-08 11:34 ` 2.6.9-rc3-mm3 Ryan Cumming
2004-10-08 7:00 ` 2.6.9-rc3-mm3 Ingo Molnar
2004-10-07 22:03 ` 2.6.9-rc3-mm3 William Lee Irwin III
2004-10-07 9:59 ` 2.6.9-rc3-mm3 Martin Zwickel
2004-10-07 10:04 ` 2.6.9-rc3-mm3 Jesper Juhl
2004-10-07 10:15 ` 2.6.9-rc3-mm3 Russell King
2004-10-07 16:58 ` 2.6.9-rc3-mm3: `risc_code_addr01' multiple definition Adrian Bunk
2004-10-07 17:29 ` Andrew Vasquez
2004-10-07 17:50 ` James Bottomley
2004-10-07 18:13 ` Andrew Vasquez
2004-10-07 18:15 ` Andrew Vasquez
2004-10-07 18:30 ` Andrew Vasquez
2004-10-21 13:02 ` Jes Sorensen [this message]
2004-10-07 17:08 ` 2.6.9-rc3-mm3 (compile stats) John Cherry
2004-10-07 20:56 ` 2.6.9-rc3-mm3 Joel Schopp
2004-10-07 21:33 ` 2.6.9-rc3-mm3 Andrew Morton
2004-10-07 21:01 ` 2.6.9-rc3-mm3: build problem on dual-Opteron w/ NUMA Rafael J. Wysocki
2004-10-07 21:40 ` Andrew Morton
2004-10-07 21:46 ` Andi Kleen
2004-10-08 10:33 ` 2.6.9-rc3-mm3: vm-thrashing-control-tuning Hideo AOKI
2004-10-08 20:49 ` Andrew Morton
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=yq08ya0rzqo.fsf@jaguar.mkp.net \
--to=jes@wildopensource.com \
--cc=James.Bottomley@SteelEye.com \
--cc=akpm@osdl.org \
--cc=andrew.vasquez@qlogic.com \
--cc=bunk@stusta.de \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®