public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: GrandMasterLee <masterlee@digitalroadkill.net>
To: Christoph Hellwig <hch@infradead.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.20-aa1 questions.
Date: 03 Dec 2002 15:01:27 -0600	[thread overview]
Message-ID: <1038949286.2047.12.camel@UberGeek> (raw)
In-Reply-To: <20021203205830.A25661@infradead.org>

On Tue, 2002-12-03 at 14:58, Christoph Hellwig wrote:
> On Tue, Dec 03, 2002 at 02:54:08PM -0600, Austin Gonyou wrote:
> > what do the following patches actually *fix*?
> > 
> > 00_backout-gcc-3_0-patch-1
> > 00_gcc-30-volatile-xtime-1
> > 
> > I'm trying to get 2.4.20 patched up by using the -aa split patches for
> > 2.4.20 and I'm incorporating only the things I want, but I use gcc 3.2
> > for compiling, and these confused me a bit.
> 
> Oooh,  I had lengthy discussion with andrea on those two.  These patches
> are a) grossly misnamed and b) should be one.  They change xtime to a volatile
> because andrea thinks that's safer.
> 
> The background on the silly naming is that earlier 2.4 kernels had xtime
> not volatile but the prototype (or vice versa) and gcc3 didn't like that.

Ahh...kewl. thanks much. I was thinking that, but I was very confused by
the naming versus the code. (not that I was *that* sure of the code
anyway, but you know.) :)



> So the best idea would be to merge them into 00_xtime_volatile-1 if
> you want to keep them.

Ok...that sounds like a plan. Thanks so much.

-- 
GrandMasterLee <masterlee@digitalroadkill.net>

  reply	other threads:[~2002-12-03 20:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-03 20:54 2.4.20-aa1 questions Austin Gonyou
2002-12-03 20:58 ` Christoph Hellwig
2002-12-03 21:01   ` GrandMasterLee [this message]
2002-12-03 21:32     ` [PATCH] 00_xtime_volatile-1 GrandMasterLee

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=1038949286.2047.12.camel@UberGeek \
    --to=masterlee@digitalroadkill.net \
    --cc=hch@infradead.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