From: Andi Kleen <ak@suse.de>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Matthew Wilcox <matthew@wil.cx>, Keith Owens <kaos@ocs.com.au>,
linux-arch@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: module compiler version check still needed?
Date: Mon, 14 Aug 2006 07:45:14 +0200 [thread overview]
Message-ID: <200608140745.14435.ak@suse.de> (raw)
In-Reply-To: <20060814053831.GA23871@mars.ravnborg.org>
On Monday 14 August 2006 07:38, Sam Ravnborg wrote:
> On Mon, Aug 14, 2006 at 06:59:49AM +0200, Andi Kleen wrote:
> >
> > > Will we remember to add the check back in when we introduce new
> > > dependencies on compiler versions?
> >
> > If something breaks it be readded. I see it only as a special
> > hack for some extraordinary, and hopefully these problems won't happen again.
> What we should add should be some kind of cabability mask.
It would be probably overkill.
> There is no need to require that modules are built with exactly the same
> compiler as the kernel when it is only a very few compiler versions that
> causes layout/ABI differences.
On i386/x86-64 that's not the case anymore as far as I know.
-Andi
next prev parent reply other threads:[~2006-08-14 5:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-13 4:48 module compiler version check still needed? Andi Kleen
2006-08-13 4:59 ` Keith Owens
2006-08-13 20:27 ` Andi Kleen
2006-08-13 22:04 ` Adrian Bunk
2006-08-13 22:14 ` Matthew Wilcox
2006-08-14 4:59 ` Andi Kleen
2006-08-14 5:38 ` Sam Ravnborg
2006-08-14 5:45 ` Andi Kleen [this message]
2006-08-14 9:06 ` Arjan van de Ven
2006-08-14 9:19 ` Andi Kleen
2006-08-14 22:11 ` 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=200608140745.14435.ak@suse.de \
--to=ak@suse.de \
--cc=kaos@ocs.com.au \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew@wil.cx \
--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 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.