From: Dave Jones <davej@suse.de>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Linus Torvalds <torvalds@transmeta.com>,
Martin Wilck <Martin.Wilck@fujitsu-siemens.com>,
Linux Kernel mailing list <linux-kernel@vger.kernel.org>,
Richard Gooch <rgooch@atnf.csiro.au>,
Marcelo Tosatti <marcelo@conectiva.com.br>
Subject: Re: [PATCH]: Fix MTRR handling on HT CPUs (improved)
Date: Fri, 25 Jan 2002 19:19:09 +0100 [thread overview]
Message-ID: <20020125191908.K28068@suse.de> (raw)
In-Reply-To: <Pine.LNX.4.33.0201241338030.15092-100000@penguin.transmeta.com> <E16UAmA-00038O-00@the-village.bc.nu>
In-Reply-To: <E16UAmA-00038O-00@the-village.bc.nu>; from alan@lxorguk.ukuu.org.uk on Fri, Jan 25, 2002 at 06:08:34PM +0000
On Fri, Jan 25, 2002 at 06:08:34PM +0000, Alan Cox wrote:
> 2.4 has a nice clean 2 line patch in to cover this or should have done
> providing it didnt get lost in the merge.
The microcode driver fix was ~2 lines. The MTRR ones I've seen
have been a little more involved. Unless you saw something I
didn't..
--
| Dave Jones. http://www.codemonkey.org.uk
| SuSE Labs
next prev parent reply other threads:[~2002-01-25 18:19 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-24 20:57 [PATCH]: Fix MTRR handling on HT CPUs (improved) Martin Wilck
2002-01-24 21:39 ` Linus Torvalds
2002-01-24 22:30 ` Dave Jones
2002-01-25 9:37 ` Martin Wilck
2002-01-25 11:05 ` Martin Wilck
2002-01-25 18:08 ` Alan Cox
2002-01-25 18:19 ` Dave Jones [this message]
2002-01-25 18:20 ` Alan Cox
2002-01-25 18:14 ` Linus Torvalds
2002-01-25 18:54 ` Alan Cox
2002-01-25 18:51 ` arjan
2002-01-25 18:57 ` Dave Jones
2002-01-25 20:40 ` Linus Torvalds
2002-01-28 8:13 ` Martin Wilck
2002-02-13 11:42 ` SMT, again (was: Re: [PATCH]: Fix MTRR handling on HT CPUs) Martin Wilck
2002-02-13 12:15 ` Alan Cox
2002-01-25 21:30 ` [PATCH]: Fix MTRR handling on HT CPUs (improved) Timothy Covell
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=20020125191908.K28068@suse.de \
--to=davej@suse.de \
--cc=Martin.Wilck@fujitsu-siemens.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
--cc=rgooch@atnf.csiro.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