From: Adrian Bunk <bunk@fs.tum.de>
To: Alan <alan@lxorguk.ukuu.org.uk>
Cc: groudier@free.fr, linux-scsi@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [2.5 patch] MegaRAID driver: remove kernel 2.0 and 2.2 code
Date: Tue, 21 Jan 2003 15:13:51 +0100 [thread overview]
Message-ID: <20030121141351.GB6870@fs.tum.de> (raw)
In-Reply-To: <1043117030.13113.15.camel@dhcp22.swansea.linux.org.uk>
On Tue, Jan 21, 2003 at 02:43:51AM +0000, Alan wrote:
> On Sat, 2003-01-18 at 16:22, Adrian Bunk wrote:
> > The patch below removes obsolete #if'd code for kernel 2.0 and 2.2 from
> > drivers/scsi/megaraid.{h,c} (this includes the expansion of some
> > #define's that were definded differently for different kernel versions).
> >
> > I've tested the compilation with 2.5.59.
>
> AMI still issue 2.2 versions of this driver so its probably excessive
> (AMI ? -- LSI now I guess)
In megaraid.c IO_LOCK_IRQ and IO_UNLOCK_IRQ are only defined for >= 2.4
(they are present since 2.5.1-pre2) and the since Al Viro's
kdev_t -> block_device * conversion you get a compile error when trying
to use megaraid.{c,h} in 2.2.23.
If it's intended that this file is still used in kernels < 2.4 some
changes are needed.
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2003-01-21 14:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-18 16:22 [2.5 patch] MegaRAID driver: remove kernel 2.0 and 2.2 code Adrian Bunk
2003-01-21 2:43 ` Alan
2003-01-21 14:13 ` Adrian Bunk [this message]
2003-01-22 4:04 ` Matt Domsch
2003-01-22 4:25 ` Matt Domsch
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=20030121141351.GB6870@fs.tum.de \
--to=bunk@fs.tum.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=groudier@free.fr \
--cc=linux-kernel@vger.kernel.org \
--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