public inbox for linux-arch@vger.kernel.org
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Andi Kleen <ak@suse.de>
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:38:31 +0200	[thread overview]
Message-ID: <20060814053831.GA23871@mars.ravnborg.org> (raw)
In-Reply-To: <200608140659.49462.ak@suse.de>

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.
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.

	Sam

  reply	other threads:[~2006-08-14  5:38 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 [this message]
2006-08-14  5:45           ` Andi Kleen
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=20060814053831.GA23871@mars.ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=ak@suse.de \
    --cc=kaos@ocs.com.au \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matthew@wil.cx \
    /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