All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Leete <tleete@mountain.net>
To: Andre Hedrick <andre@linux-ide.org>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>, David Ford <david@linux.com>,
	Stephen Frost <sfrost@snowman.net>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: 2.4.x and SMP fails to compile (`current' undefined)
Date: Thu, 01 Feb 2001 08:39:39 -0500	[thread overview]
Message-ID: <3A79671B.8A1BD249@mountain.net> (raw)
In-Reply-To: <Pine.LNX.4.10.10102010011530.15351-100000@master.linux-ide.org>

Andre Hedrick wrote:
> 
> Make it and I will care and post it on kernel.org for you.
> I need that patch soon.
> 
> On Thu, 1 Feb 2001, Tom Leete wrote:
> 
> > Alan Cox wrote:
> > > The string.h code was fine, someone came along and put in a ridiculous loop
> > > in the include dependancies and broke it. Nobody has had the time to untangle
> > > it cleanly since
> >
> > Yes, bitrot. I don't see a rearrangement of system headers happening in 2.4.
> > I'm pretty sure if I committed such a patch it would have no measurable
> > lifetime.

Hi Andre,

I meant that nobody should be reshuffling 2.4 headers now, didn't intend to
sound like I take that personally.

I'll take a look. I may be able to do something with include guards or other
#defines + multiple passes. We already have the multiple passes.

I think my arguments for the present patch are good. I'm making a mod of
Arjan's athlon.c to see if I'm right. If you have a suggestion for another
benchmark, I'd like to hear about it. Whatever the results, I'll post them
here.

Glad if whatever comes out is useful to you.

Cheers,
Tom

-- 
The Daemons lurk and are dumb. -- Emerson
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2001-02-01 13:40 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-31  2:53 2.4.x and SMP fails to compile (`current' undefined) David Ford
2001-01-31  3:01 ` Stephen Frost
2001-01-31  4:37   ` David Ford
2001-01-31  7:16     ` Peter Samuelson
2001-01-31  8:03     ` Tom Leete
2001-01-31 10:26       ` Peter Samuelson
2001-01-31 10:48         ` Tom Leete
2001-01-31 11:10           ` Peter Samuelson
2001-01-31 23:01             ` Olaf Titz
2001-01-31 23:38           ` David Lang
2001-02-01  1:11             ` Peter Samuelson
2001-02-01  1:22               ` Alan Cox
2001-02-02 15:12         ` Pavel Machek
2001-01-31 13:29       ` Alan Cox
2001-02-01  7:52         ` Tom Leete
2001-02-01  8:12           ` Andre Hedrick
2001-02-01 13:39             ` Tom Leete [this message]
2001-02-01 10:50           ` Alan Cox
2001-02-01 13:53             ` Tom Leete
2001-01-31 23:26     ` David Lang
2001-02-01 15:04       ` Jeff Garzik

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=3A79671B.8A1BD249@mountain.net \
    --to=tleete@mountain.net \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=andre@linux-ide.org \
    --cc=david@linux.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sfrost@snowman.net \
    /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.