From: Pavel Machek <pavel@ucw.cz>
To: Frans Pop <elendil@planet.nl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.34-rc3: Can't insmod after make, because versions now differ?!
Date: Tue, 6 Apr 2010 15:26:22 +0200 [thread overview]
Message-ID: <20100406132622.GA1366@ucw.cz> (raw)
In-Reply-To: <201004061500.32569.elendil@planet.nl>
On Tue 2010-04-06 15:00:31, Frans Pop wrote:
> On Tuesday 06 April 2010, Pavel Machek wrote:
> > Yes, but... should module version checking be fixed so that it does
> > not interfere like that?
>
> I don't think so. Essentially you are getting what you configured: an
> extremely fine-grained kernel version. It's up to you to decide whether
> the benefits of that outweigh the limitations it brings.
Yes, I want descriptive version strings. And yes, I'd like to use
modules, and do development.
Unfortunately, these two seem mutually exclusive. Given that Linus
made noises (iirc) about 'everyone should set localversion_auto'...
> Stripping parts of the kernel version for module compatibility checks could
> interfere with suffixes explicitly added by distros to specify ABI
> compatibility.
So split the version into regular parts and very detailed parts,
putting explicit user options into 'regular'?
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
prev parent reply other threads:[~2010-04-06 13:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-05 5:36 2.6.34-rc3: Can't insmod after make, because versions now differ?! Pavel Machek
2010-04-05 6:45 ` Andreas Mohr
2010-04-05 15:24 ` Frans Pop
2010-04-06 7:06 ` Pavel Machek
2010-04-06 13:00 ` Frans Pop
2010-04-06 13:26 ` Pavel Machek [this message]
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=20100406132622.GA1366@ucw.cz \
--to=pavel@ucw.cz \
--cc=elendil@planet.nl \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.