public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@steeleye.com>
To: Andrew Vasquez <andrew.vasquez@qlogic.com>
Cc: SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: RE: Qlogic qla2xxx driver up for testing
Date: 19 May 2003 19:01:29 -0500	[thread overview]
Message-ID: <1053388889.1826.50.camel@mulgrave> (raw)
In-Reply-To: <B179AE41C1147041AA1121F44614F0B060EC1D@AVEXCH02.qlogic.org>

On Mon, 2003-05-19 at 18:43, Andrew Vasquez wrote:
> I've just uploaded a new version of the driver to the SF site that
> fixes the 21xx/22xx build problems:
> 
> 	http://marc.theaimsgroup.com/?l=linux-scsi&m=105338567812190&w=2
>  
> > The qla2xxx/Makefile is rather convoluted, and makes it look like
> > building more than one type of driver non-modular may be a problem.
> >

OK, I'll take a look.

> I'm not entirely thrilled with the build process.  Trying to shoehorn
> kbuild into builing three driver binaries was a real mess.  Also, you
> are correct, building more than one driver in a non-modular 
> fashion currently fails -- redefinitions of symbols... (modular builds 
> of the drivers work fine).
> 
> I've read the documentation in kbuild/makefiles.txt, but unfortuantely,
> given the form and structure of the driver sources, I've yet to fashion 
> a simpler build method for the drivers,  any suggestions?

What about simply making it a runtime instead of compile time determined
thing?  None of the #ifdefs looks to occur in a region of code that's
that critical.

If you're worried about firmware size, you could put that into a discard
section.

James


       reply	other threads:[~2003-05-19 23:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <B179AE41C1147041AA1121F44614F0B060EC1D@AVEXCH02.qlogic.org>
2003-05-20  0:01 ` James Bottomley [this message]
2003-05-19 21:11 Qlogic qla2xxx driver up for testing James Bottomley
2003-05-19 23:44 ` Andrew Vasquez

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=1053388889.1826.50.camel@mulgrave \
    --to=james.bottomley@steeleye.com \
    --cc=andrew.vasquez@qlogic.com \
    --cc=linux-scsi@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