mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: Andi Kleen <ak@muc.de>
Cc: torvalds@transmeta.com, akpm@digeo.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Remove spinlock workaround for pre 2.95 gccs
Date: Fri, 20 Jun 2003 13:00:56 +1000	[thread overview]
Message-ID: <20030620030225.952512C05E@lists.samba.org> (raw)
In-Reply-To: Your message of "Thu, 19 Jun 2003 23:18:19 +0200." <20030619211819.GA12716@averell>

In message <20030619211819.GA12716@averell> you write:
> Advantage is that gcc 2.95 and 3.x compiled kernels are now binary
> compatible. Unfortunately module loading still checks the compiler
> version, but I guess that could be taken out now. As far as I know
> there should be no compiler related incompatibilities now.

Good point, Andi.  And if any particular arch has compiler version
issues it can add it back in the arch-specific part.

Patch is as trivial.  If noone else can think of any problems?
Cheers,
Rusty.

diff -urpN --exclude TAGS -X /home/rusty/devel/kernel/kernel-patches/current-dontdiff --minimal linux-2.5.72-bk2/include/linux/vermagic.h working-2.5.72-bk2-compiler-version/include/linux/vermagic.h
--- linux-2.5.72-bk2/include/linux/vermagic.h	2003-02-18 11:18:56.000000000 +1100
+++ working-2.5.72-bk2-compiler-version/include/linux/vermagic.h	2003-06-20 12:57:51.000000000 +1000
@@ -19,5 +19,4 @@
 #define VERMAGIC_STRING 						\
 	UTS_RELEASE " "							\
 	MODULE_VERMAGIC_SMP MODULE_VERMAGIC_PREEMPT 			\
-	MODULE_ARCH_VERMAGIC 						\
-	"gcc-" __stringify(__GNUC__) "." __stringify(__GNUC_MINOR__)
+	MODULE_ARCH_VERMAGIC

--
  Anyone who quotes me in their sig is an idiot. -- Rusty Russell.

      reply	other threads:[~2003-06-20  2:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-19 21:18 Andi Kleen
2003-06-20  3:00 ` Rusty Russell [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=20030620030225.952512C05E@lists.samba.org \
    --to=rusty@rustcorp.com.au \
    --cc=ak@muc.de \
    --cc=akpm@digeo.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.com \
    /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®