From: Patrick McFarland <diablod3@gmail.com>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: RFC: Testing for kernel features in external modules
Date: Thu, 24 Jun 2004 16:24:01 -0400 [thread overview]
Message-ID: <d577e569040624132413451e20@mail.gmail.com> (raw)
In-Reply-To: <20040624203043.GA4557@mars.ravnborg.org>
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?
--
Patrick "Diablo-D3" McFarland || diablod3@gmail.com
"Computer games don't affect kids; I mean if Pac-Man affected us as kids, we'd
all be running around in darkened rooms, munching magic pills and listening to
repetitive electronic music." -- Kristian Wilson, Nintendo, Inc, 1989
next prev parent reply other threads:[~2004-06-24 20:24 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 [this message]
2004-06-24 20:49 ` Sam Ravnborg
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=d577e569040624132413451e20@mail.gmail.com \
--to=diablod3@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.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