From: Arjan van de Ven <arjan@infradead.org>
To: Petr Vandrovec <vandrove@vc.cvut.cz>
Cc: Sam Ravnborg <sam@ravnborg.org>,
Petr Vandrovec <petr@vandrovec.name>,
David Woodhouse <dwmw2@infradead.org>,
torvalds@osdl.org, akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [GIT *] Remove inclusion of obsolete <linux/config.h>
Date: Wed, 12 Jul 2006 14:51:29 +0200 [thread overview]
Message-ID: <1152708689.3217.36.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <44B4D666.706@vc.cvut.cz>
On Wed, 2006-07-12 at 13:00 +0200, Petr Vandrovec wrote:
> Sam Ravnborg wrote:
> >>FYI, fortunately (for you, unfortunately for VMware) 2.6.18's already broke
> >>our build script due to UTS_RELEASE being moved to separate file, so from
> >>VMware's viewpoint killconfig.h.git will not do any additional damage...
> >
> > #include <linux/config.h>
> > #ifndef UTS_RELEASE
> > #include <linux/utsrelease.h>
> > #endif
> >
> > Then one can wonder why WMware needs UTS_RELEASE?
>
> To make sure user is building modules for kernel it is really using. Without
> this test users were building modules for kernels they have run years ago, and
> then complained that modules do not fit to running kernel, or that kernel
> crashes when they do 'insmod -f ...'... So perl wrapper passes linux/version.h
> through C preprocessor and compares resulting UTS_RELEASE with `uname -r`, and
> complains loudly if they do not match.
>
isn't this exactly what VERMAGIC is for instead?
next prev parent reply other threads:[~2006-07-12 12:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-11 15:28 David Woodhouse
2006-07-11 23:35 ` Petr Vandrovec
2006-07-12 3:37 ` Sam Ravnborg
2006-07-12 11:00 ` Petr Vandrovec
2006-07-12 12:51 ` Arjan van de Ven [this message]
2006-07-12 13:54 ` Petr Vandrovec
-- strict thread matches above, loose matches on Subject: below --
2006-07-06 13:07 David Woodhouse
2006-07-06 13:11 ` David Woodhouse
2006-07-06 17:29 ` Greg KH
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=1152708689.3217.36.camel@laptopd505.fenrus.org \
--to=arjan@infradead.org \
--cc=akpm@osdl.org \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=petr@vandrovec.name \
--cc=sam@ravnborg.org \
--cc=torvalds@osdl.org \
--cc=vandrove@vc.cvut.cz \
/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
all inboxes | Powered by JetHome®