public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: Timur Tabi <ttabi@interactivesi.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Pls add this driver to the kernel tree !!
Date: Fri, 01 Dec 2000 09:26:29 +0000	[thread overview]
Message-ID: <24827.975662789@redhat.com> (raw)
In-Reply-To: <20001130203703Z129437-440+118@vger.kernel.org>
In-Reply-To: <20001130203703Z129437-440+118@vger.kernel.org>  <200011301803.eAUI3Pu16137@webber.adilger.net>


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. 

--
dwmw2


-
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/

  parent reply	other threads:[~2000-12-01 10:00 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 [this message]
2000-12-01 19:43       ` David Schleef
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=24827.975662789@redhat.com \
    --to=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