All of lore.kernel.org
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@redhat.com>
To: rml@tech9.net
Cc: torvalds@transmeta.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] spinlock.h cleanup
Date: Mon, 29 Jul 2002 19:19:31 -0700 (PDT)	[thread overview]
Message-ID: <20020729.191931.45561787.davem@redhat.com> (raw)
In-Reply-To: <1027989220.1016.273.camel@sinai>

   From: Robert Love <rml@tech9.net>
   Date: 29 Jul 2002 17:33:39 -0700

   On Mon, 2002-07-29 at 17:30, Robert Love wrote:
   
   > On Mon, 2002-07-29 at 17:26, Linus Torvalds wrote:
   > 
   > > Hmm.. Why did you remove the gcc workaround? Are all gcc's > 2.95 known to 
   > > be ok wrt empty initializers?
   > 
   > If I recall correctly, the fix was for older egcs compilers.
   
   To better answer your question, I just checked and indeed it seems all
   gcc's >= 2.95 are OK.

Some platforms (sparc64) are still using things like egcs-2.92.x
vintage compilers as their main supported kernel build compiler.

init/main.c allows 2.91 or greater to pass so that should be the rule
enforced kernel wide.

I don't remember when the empty initializer thing was fixed.

  parent reply	other threads:[~2002-07-30  2:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-30  0:01 [PATCH] spinlock.h cleanup Robert Love
2002-07-30  0:26 ` Linus Torvalds
2002-07-30  0:30   ` Robert Love
2002-07-30  0:33     ` Robert Love
2002-07-30  1:06       ` Robert Love
2002-07-30  2:19       ` David S. Miller [this message]
2002-07-30  1:46     ` Linus Torvalds
2002-07-30  1:48       ` Arnaldo Carvalho de Melo
2002-07-30  1:49       ` Robert Love

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=20020729.191931.45561787.davem@redhat.com \
    --to=davem@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rml@tech9.net \
    --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 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.