public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Patrick McFarland <diablod3@gmail.com>
Cc: Sam Ravnborg <sam@ravnborg.org>, linux-kernel@vger.kernel.org
Subject: Re: RFC: Testing for kernel features in external modules
Date: Thu, 24 Jun 2004 22:49:52 +0200	[thread overview]
Message-ID: <20040624204952.GA4700@mars.ravnborg.org> (raw)
In-Reply-To: <d577e569040624132413451e20@mail.gmail.com>

On Thu, Jun 24, 2004 at 04:24:01PM -0400, Patrick McFarland wrote:
> On Thu, 24 Jun 2004 22:30:43 +0200, Sam Ravnborg <sam@ravnborg.org> wrote:
> > 
> > The last couple of kbuild patches has put attention to testing for
> > features in the kernel so an external modules can stay compatible
> > with a broad range of kernels.
> > Since vendors backport patches then testing for the kernel version is not
> > an option, so other means are reqired.
> > 
> > Two approaches are in widespread use:
> > a) grep kernel headers
> > b) Try to compile a small .c file (nvidia is a good example)
> 
> Why can't you check the .config file to see if features are enabled?

Features in a broad sense so API changes with respect to types
and function calls

	Sam

  reply	other threads:[~2004-06-24 20:38 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-24 20:30 RFC: Testing for kernel features in external modules Sam Ravnborg
2004-06-24 20:24 ` Patrick McFarland
2004-06-24 20:49   ` Sam Ravnborg [this message]
2004-06-24 20:35 ` Andreas Dilger
2004-06-24 21:07   ` Gerd Knorr
2004-06-24 21:23   ` Sam Ravnborg
2004-06-25  8:32   ` Andreas Gruenbacher
2004-06-25  9:04     ` Lars Marowsky-Bree
2004-06-26 23:48       ` Adrian Bunk

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=20040624204952.GA4700@mars.ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=diablod3@gmail.com \
    --cc=linux-kernel@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