From: David Schleef <ds@stm.lbl.gov>
To: David Woodhouse <dwmw2@infradead.org>
Cc: Timur Tabi <ttabi@interactivesi.com>, linux-kernel@vger.kernel.org
Subject: Re: Pls add this driver to the kernel tree !!
Date: Fri, 1 Dec 2000 11:43:47 -0800 [thread overview]
Message-ID: <20001201114347.A3439@stm.lbl.gov> (raw)
In-Reply-To: <20001130203703Z129437-440+118@vger.kernel.org> <200011301803.eAUI3Pu16137@webber.adilger.net> <20001130203703Z129437-440+118@vger.kernel.org> <24827.975662789@redhat.com>
In-Reply-To: <24827.975662789@redhat.com>; from dwmw2@infradead.org on Fri, Dec 01, 2000 at 09:26:29AM +0000
On Fri, Dec 01, 2000 at 09:26:29AM +0000, David Woodhouse wrote:
>
> ttabi@interactivesi.com said:
> > Not necessarily - it all depends on what your driver does. In many
> > cases, supporting 2.2 and 2.4 is easy, and all you need are a few
> > #if's. It's certainly much better to have a dozen or so #if's
> > sprinkled throughout the code than to have two separate source trees,
> > and have to make the same change to multiple files.
>
> It's even better to do it without the ugly preprocessor magic - see
> include/linux/compatmac.h
>
> There are a few things missing from there - include/linux/mtd/compatmac.h
> has more. One day we'll get round to removing the latter and merging it
> into the main one, hopefully.
A while ago, I started working on the Mother Of All compatmac.h files,
trying to merge Don Becker's stuff, yours, David Hinds, and stuff
from my own Comedi package. It quickly got out of control, as
including compatmac.h (or kern_compat.h, as I called it) would
include most of the include/linux directory. I've since settled for
setting up a separate include/linux tree with header files
named pci.h, mm.h, etc., that #define the right things and then
do an #include_next. Interested parties can find it in Comedi
(http://stm.lbl.gov/comedi).
dave...
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-12-01 20:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-28 2:51 Pls add this driver to the kernel tree !! John B. Jacobsen
2000-11-30 17:19 ` Tigran Aivazian
2000-11-30 17:32 ` Meelis Roos
2000-11-30 18:03 ` Andreas Dilger
2000-11-30 19:16 ` Mark Hahn
2000-11-30 20:41 ` Alan Cox
2000-11-30 20:06 ` Timur Tabi
2000-12-01 9:26 ` David Woodhouse
2000-12-01 19:43 ` David Schleef [this message]
2000-12-01 17:25 ` Jeff Garzik
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=20001201114347.A3439@stm.lbl.gov \
--to=ds@stm.lbl.gov \
--cc=ds@schleef.org \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ttabi@interactivesi.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