From: Christoph Hellwig <hch@lst.de>
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: Christoph Hellwig <hch@lst.de>,
Jes Sorensen <jes@wildopensource.com>,
SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: qla1280 compile problems
Date: Tue, 5 Aug 2003 18:31:03 +0200 [thread overview]
Message-ID: <20030805163103.GA28693@lst.de> (raw)
In-Reply-To: <1060100259.2044.3.camel@fuzzy>
On Tue, Aug 05, 2003 at 09:17:38AM -0700, James Bottomley wrote:
> On Tue, 2003-08-05 at 05:18, Christoph Hellwig wrote:
> > The qla1280 update still has some issues, mostly because it backs
> > out all the 2.5 changes applied to the driver in the last months,
> > also it doesn't work on ia64 because the IA64 generic build references
> > sn2-specific symbols that don't exist in that build.
>
> Could you be more explicit on this? I thought I'd re-added all of the
> backed out patches (although I might have missed some).
These seem to be missing at least
- remove all #include <linux/blk.h>'s (Adrian Bunk)
- give ->proc_info a struct Scsi_Host * paramter (me)
- move all host templates into .c files (me)
- Spellig fixes for consistent, dependent and persistent
- Spellig fixes
- [patch, 2.5] scsi_qla1280.c free on error path
> For what it's worth, this compiled for me without warnings on parisc64
> (although I haven't got around to actually testing it).
strange, I can's see how it could compile at least with the superflous
initializer for sht.command.
next prev parent reply other threads:[~2003-08-05 16:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-05 12:18 qla1280 compile problems Christoph Hellwig
2003-08-05 12:40 ` Jes Sorensen
2003-08-05 12:49 ` Christoph Hellwig
2003-08-05 12:54 ` Jes Sorensen
2003-08-05 16:17 ` James Bottomley
2003-08-05 16:31 ` Christoph Hellwig [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-08-05 12:15 Christoph Hellwig
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=20030805163103.GA28693@lst.de \
--to=hch@lst.de \
--cc=James.Bottomley@SteelEye.com \
--cc=jes@wildopensource.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