From: Andi Kleen <ak@muc.de>
To: Riley Williams <Riley@Williams.Name>
Cc: Andi Kleen <ak@muc.de>,
torvalds@transmeta.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Support worst case cache line sizes as config option
Date: Sun, 27 Apr 2003 14:52:38 +0200 [thread overview]
Message-ID: <20030427125238.GA1083@averell> (raw)
In-Reply-To: <BKEGKPICNAKILKJKMHCAAEPNCIAA.Riley@Williams.Name>
On Sun, Apr 27, 2003 at 01:36:45PM +0200, Riley Williams wrote:
> Does the order of those "default" lines actually matter?
> Your moving that one to the top of the list appears to imply that it does.
I don't know if it matters, probably not.
-Andi
next prev parent reply other threads:[~2003-04-27 12:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-27 2:23 [PATCH] Support worst case cache line sizes as config option Andi Kleen
[not found] ` <BKEGKPICNAKILKJKMHCAAEPNCIAA.Riley@Williams.Name>
2003-04-27 12:52 ` Andi Kleen [this message]
2003-04-28 9:16 ` Adrian Bunk
2003-04-28 11:47 ` Andi Kleen
2003-04-28 12:19 ` Adrian Bunk
2003-04-28 12:48 ` Jamie Lokier
2003-04-28 22:00 ` Andi Kleen
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=20030427125238.GA1083@averell \
--to=ak@muc.de \
--cc=Riley@Williams.Name \
--cc=linux-kernel@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).