From: Robert Love <rml@tech9.net>
To: Dave Jones <davej@suse.de>
Cc: Rainer Keller <Keller@hlrs.de>,
linux-kernel@vger.kernel.org,
Marcelo Tosatti <marcelo@conectiva.com.br>
Subject: Re: [PATCH] Small optimization for UP in sched and prefetch
Date: 11 Jan 2002 15:07:06 -0500 [thread overview]
Message-ID: <1010779627.815.0.camel@phantasy> (raw)
In-Reply-To: <Pine.LNX.4.33.0201112101290.31366-100000@wotan.suse.de>
In-Reply-To: <Pine.LNX.4.33.0201112101290.31366-100000@wotan.suse.de>
On Fri, 2002-01-11 at 15:02, Dave Jones wrote:
> It's handled a few lines further down in a CONFIG_X86_USE_3DNOW
> which means that CyrixIII's can also use them too.
Ah, my mistake. I should of read the source and not just the patch.
Robert Love
prev parent reply other threads:[~2002-01-11 20:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-11 10:33 [PATCH] Small optimization for UP in sched and prefetch Rainer Keller
2002-01-11 10:51 ` Jeff Garzik
2002-01-11 17:07 ` [PATCH] Small optimization for UP in sched and prefetch (take 3) Rainer Keller
2002-01-11 19:59 ` [PATCH] Small optimization for UP in sched and prefetch Robert Love
2002-01-11 20:02 ` Dave Jones
2002-01-11 20:07 ` Robert Love [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=1010779627.815.0.camel@phantasy \
--to=rml@tech9.net \
--cc=Keller@hlrs.de \
--cc=davej@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
/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