public inbox for linux-arch@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: Keith Owens <kaos@ocs.com.au>
Cc: linux-arch@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: module compiler version check still needed?
Date: Sun, 13 Aug 2006 22:27:24 +0200	[thread overview]
Message-ID: <200608132227.24719.ak@suse.de> (raw)
In-Reply-To: <31645.1155445159@ocs10w.ocs.com.au>

On Sunday 13 August 2006 06:59, Keith Owens wrote:
> Andi Kleen (on Sun, 13 Aug 2006 06:48:36 +0200) wrote:
> >
> >Does anybody know of any reason why we would still need the compiler version
> >check during module loading? AFAIK on i386 it was only needed to handle
> >2.95 (which got dropped) and on x86-64 it was never needed. Is there
> >a need on any other architecture for it?
> 
> IA64 still needs the check.  include/asm-ia64/spinlock.h generates
> different calls to the out of line spinlock handler, depending on the
> version of gcc.

Thanks. But I guess it could be used to MODULE_ARCH_VERMAGIC for ia64 only then.
If nobody else complains I will do that.

-Andi

  reply	other threads:[~2006-08-13 20:27 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 [this message]
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
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=200608132227.24719.ak@suse.de \
    --to=ak@suse.de \
    --cc=kaos@ocs.com.au \
    --cc=linux-arch@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox