public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@conectiva.com.br>
To: Rusty Russell <rusty@rustcorp.com.au>,
	Linus Torvalds <torvalds@transmeta.com>
Cc: miles@gnu.org, kaos@ocs.com.au, linux-kernel@vger.kernel.org
Subject: Re: [PATCH][RFC] PentiumPro/II split in x86 config
Date: Wed, 29 May 2002 01:27:53 -0300	[thread overview]
Message-ID: <20020529042753.GC28492@conectiva.com.br> (raw)
In-Reply-To: <3937.1022552654@kao2.melbourne.sgi.com> <buo3cwdf0b0.fsf@mcspd15.ucom.lsi.nec.co.jp> <20020528030200.GL20729@conectiva.com.br> <20020529142350.7cc6cc59.rusty@rustcorp.com.au>

Em Wed, May 29, 2002 at 02:23:50PM +1000, Rusty Russell escreveu:
> On Tue, 28 May 2002 00:02:00 -0300
> Arnaldo Carvalho de Melo <acme@conectiva.com.br> wrote:
> 
> > Em Tue, May 28, 2002 at 11:55:47AM +0900, Miles Bader escreveu:
> > > Keith Owens <kaos@ocs.com.au> writes:
> > > > The kernel can only be compiled with gcc, but some bits of the build
> > > > are compiled and run on the host, using the host compiler.  Avoid using
> > > > gccisms where there is a standard way of doing it.
> > > 
> > > That particular gccism completely infests the kernel, so there seems
> > > little point in avoiding it in favor of the uglier standard syntax.
> > 
> > Agreed.
> > 
> > What I'll do: continue using the simpler way that only gcc understands but
> > take care to not use gccisms when and if I patch build bits.
> 
> WARNING: The older form is deprecated.  From the info pages:
> 
> 	Another syntax which has the same meaning, obsolete since GCC 2.5, is
> `FIELDNAME:', as shown here:
> 
> Janitors wanted,

Ouch, Rusty, I'll reread the info pages and go over all the tree and start
submitting patches, starting tomorrow. Expect that sound, multiple times.

Powers that be: holler now or...

- Arnaldo

  reply	other threads:[~2002-05-29 10:54 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-27 14:54 [PATCH][RFC] PentiumPro/II split in x86 config J.A. Magallon
2002-05-27 17:31 ` Alan Cox
2002-05-27 21:59   ` J.A. Magallon
2002-05-28  1:29     ` Arnaldo Carvalho de Melo
2002-05-28  2:05       ` Keith Owens
2002-05-28  2:16         ` Arnaldo Carvalho de Melo
2002-05-28  2:24           ` Keith Owens
2002-05-28  2:35             ` Arnaldo Carvalho de Melo
2002-05-28  2:55             ` Miles Bader
2002-05-28  3:02               ` Arnaldo Carvalho de Melo
2002-05-28 14:03                 ` J.A. Magallon
2002-05-28 14:30                   ` Mikael Pettersson
2002-05-28 15:00                     ` David Woodhouse
2002-05-28 18:39                       ` Albert D. Cahalan
2002-05-28 16:16                     ` Miles Bader
2002-05-28 14:45                   ` Roland Dreier
2002-05-29  4:23                 ` Rusty Russell
2002-05-29  4:27                   ` Arnaldo Carvalho de Melo [this message]
2002-05-29 14:06       ` Dave Jones
2002-05-28  0:15 ` Keith Owens

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=20020529042753.GC28492@conectiva.com.br \
    --to=acme@conectiva.com.br \
    --cc=kaos@ocs.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miles@gnu.org \
    --cc=rusty@rustcorp.com.au \
    --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