From: James Bottomley <James.Bottomley@steeleye.com>
To: "Justin T. Gibbs" <gibbs@btc.adaptec.com>
Cc: SCSI Mailing List <linux-scsi@vger.kernel.org>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@transmeta.com>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Marcelo Tosatti <marcelo@conectiva.com.br>
Subject: Re: Aic7xxx and Aic79xx Driver Updates
Date: 02 May 2003 09:30:35 -0500 [thread overview]
Message-ID: <1051885837.1820.34.camel@mulgrave> (raw)
In-Reply-To: <1866260000.1051828092@aslan.btc.adaptec.com>
First off, could you take a look at
http://bugzilla.kernel.org/show_bug.cgi?id=608
I thought it was an sr problem, but it doesn't seem to show up on
anything other than adaptec controllers? Thanks.
On Thu, 2003-05-01 at 17:28, Justin T. Gibbs wrote:
> ChangeSet
> 1.1118.33.5 03/04/24 15:12:48 gibbs@overdrive.btc.adaptec.com +7 -0
> Aic7xxx and Aic79xx Driver Updates
> o Adapt to new IRQ handler declaration/behavior for 2.5.X
The changes for this:
+#if LINUX_VERSION_CODE >= KERNEL_VERSION(2,5,0)
+#define AIC_LINUX_IRQRETURN_T irqreturn_t
+#define AIC_LINUX_IRQRETURN(ours) return (IRQ_RETVAL(ours))
+#else
+#define AIC_LINUX_IRQRETURN_T void
+#define AIC_LINUX_IRQRETURN(ours) return
+#endif
Are rather convoluted. Could you just remove the wrappering for 2.5?
> ChangeSet
> 1.971.94.5 03/04/24 11:46:55 gibbs@overdrive.btc.adaptec.com +2 -0
> Aic7xxx and Aic79xx driver updates
> o Work around peculiarities in the scan_scsis routines
> that could, due to having duplicate devices on our
> host's device list, cause tagged queing to be disabled
> for devices added via /proc.
-ahc_linux_select_queue_depth(struct Scsi_Host * host,
- Scsi_Device * scsi_devs)
+ahc_linux_select_queue_depth(struct Scsi_Host *host, Scsi_Device
*scsi_devs)
select_queue_depth isn't a 2.5 interface anymore, why do you even still
need it?
> ChangeSet
> 1.971.94.3 03/04/24 11:24:15 gibbs@overdrive.btc.adaptec.com +6 -0
> Aic7xxx and Aic79xx driver Update
> o Avoid pre-2.5.X mid-layer deadlock due to SCSI malloc fragmentation
[...]
This is entirely irrelevant to 2.5 as well.
James
next prev parent reply other threads:[~2003-05-02 14:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-01 22:28 Aic7xxx and Aic79xx Driver Updates Justin T. Gibbs
2003-05-02 0:17 ` Willy Tarreau
2003-05-02 4:25 ` Justin T. Gibbs
2003-05-02 5:56 ` Willy Tarreau
2003-05-02 14:30 ` James Bottomley [this message]
2003-05-02 17:51 ` Justin T. Gibbs
2003-05-02 18:07 ` James Bottomley
2003-05-02 18:19 ` Linus Torvalds
2003-05-03 23:03 ` Justin T. Gibbs
2003-05-03 23:01 ` Justin T. Gibbs
[not found] <200212210334.gBL3Yi111607@localhost.localdomain>
[not found] ` <175810000.1041300864@aslan.btc.adaptec.com>
2003-01-08 3:46 ` Aic7xxx and Aic79xx driver updates Justin T. Gibbs
2003-01-08 3:49 ` Justin T. Gibbs
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=1051885837.1820.34.camel@mulgrave \
--to=james.bottomley@steeleye.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=gibbs@btc.adaptec.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
--cc=torvalds@transmeta.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox