From: Steve Ralston <sjralston1@cox.net>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-scsi@vger.kernel.org
Subject: Re: [TRIVIAL] warning cleanup for drivers_scsi_qla1280.c
Date: Wed, 07 Aug 2002 06:12:04 -0500 [thread overview]
Message-ID: <3D510084.3040708@cox.net> (raw)
In-Reply-To: 1028720225.18156.246.camel@irongate.swansea.linux.org.uk
On 08/07/2002 06:37 AM, Alan Cox wrote:
>General policy - rip out version ifdefs unless the driver has a
>maintainer who actively objects ?
>
Hi Alan,
When I worked for LSI, and was actively maintaining
drivers/message/fusion/...
code, we had a single set of driver source code that compiled and ran
across lots of linux kernels (2.2.5 thru 2.4.19). Most of the
version-specific
#ifdef's were isolated to one header file (linux_compat.h). We then
also had
a set of patch files (each pretty small) that could be applied against
any explicit
kernel (in the supported range). A customer could then (in theory:-)
download
one set of driver source (including the patch file sets), untar/overlay it,
apply a single patch file, and then compile+run the drivers on any of
those kernels.
So just curious, are you saying that you'd rather have driver maintainers
maintain a separate set of driver source for each explicit kernel (with no
version-specific #ifdef's) vs. the way we did it above?
Thanks,
-SteveR
next prev parent reply other threads:[~2002-08-07 11:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-07 3:59 [TRIVIAL] warning cleanup for drivers_scsi_qla1280.c Rusty Trivial Russell
2002-08-07 11:37 ` Alan Cox
2002-08-07 11:12 ` Steve Ralston [this message]
2002-08-07 13:24 ` Alan Cox
2002-08-08 2:12 ` Rusty Russell
-- strict thread matches above, loose matches on Subject: below --
2002-08-20 8:33 Rusty Trivial Russell
2002-12-16 6:43 Rusty Trivial Russell
2003-02-06 3:00 Rusty Trivial Russell
2003-06-23 6:47 Rusty Trivial Russell
2003-06-23 8:45 ` Christoph Hellwig
2003-06-23 8:51 ` Jes Sorensen
2003-06-23 9:27 ` Rusty Russell
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=3D510084.3040708@cox.net \
--to=sjralston1@cox.net \
--cc=alan@lxorguk.ukuu.org.uk \
--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