From: "Justin T. Gibbs" <gibbs@scsiguy.com>
To: Linus Torvalds <torvalds@transmeta.com>,
James Bottomley <James.Bottomley@SteelEye.com>
Cc: SCSI Mailing List <linux-scsi@vger.kernel.org>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Marcelo Tosatti <marcelo@conectiva.com.br>
Subject: Re: Aic7xxx and Aic79xx Driver Updates
Date: Sat, 03 May 2003 17:03:11 -0600 [thread overview]
Message-ID: <1430760000.1052002991@aslan.scsiguy.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0305021117270.1667-100000@home.transmeta.com>
> On 2 May 2003, James Bottomley wrote:
>>
>> I'm not asking for any changes to the way you do 2.4, just for 2.5 where
>> we have no vendor versions to support and there should only be a single
>> tree.
>
> The way the backwards-compatibility is _meant_ to work is that a driver
> can just do this:
>
> #ifndef IRQ_RETVAL
> typedef void irqreturn_t;
> #define IRQ_NONE
> #define IRQ_HANDLED
> #define IRQ_RETVAL(x)
> #endif
I switched the drivers to using this yesterday.
#ifndef IRQ_RETVAL
typedef void irqreturn_t;
#define IRQ_RETVAL(x)
#endif
Updated BK send and tar files are here:
http://people.FreeBSD.org/~gibbs/linux/SRC/
--
Justin
next prev parent reply other threads:[~2003-05-03 22:50 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
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 [this message]
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=1430760000.1052002991@aslan.scsiguy.com \
--to=gibbs@scsiguy.com \
--cc=James.Bottomley@SteelEye.com \
--cc=alan@lxorguk.ukuu.org.uk \
--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