LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: lsorense@csclub.uwaterloo.ca (Lennart Sorensen)
To: Adrian Bunk <bunk@stusta.de>
Cc: Linus Torvalds <torvalds@osdl.org>, Andrew Morton <akpm@osdl.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	takada <takada@mbf.nifty.com>,
	Jordan Crouse <jordan.crouse@amd.com>
Subject: Re: 2.6.20-rc5: known unfixed regressions (v3) (part 2)
Date: Wed, 24 Jan 2007 11:57:09 -0500	[thread overview]
Message-ID: <20070124165708.GF7582@csclub.uwaterloo.ca> (raw)
In-Reply-To: <20070124163801.GM17836@stusta.de>

On Wed, Jan 24, 2007 at 05:38:01PM +0100, Adrian Bunk wrote:
> Was the removed
>   setCx86(CX86_CCR3, ccr3);
> without any effects?

I didn't think that was ever checked in.  I thought the patch was still
being discussed.

The line missing will not as far as I can see cause any problems, it
will leave some registers accessible that normaly are not, but unless
something was to try and access them that shouldn't matter.  It is of
course more correct to reprotect them after the required changes are
done so it should be put back (if it was ever actually removed).

--
Len Sorensen

  reply	other threads:[~2007-01-24 16:57 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-12 19:27 Linux v2.6.20-rc5 Linus Torvalds
2007-01-12 22:26 ` Andrew Morton
2007-01-13  2:26   ` Nigel Cunningham
2007-01-13  3:36   ` Jeff Chua
2007-01-13  3:44     ` Jeff Chua
2007-01-13 20:23       ` Bill Davidsen
2007-01-13 23:58     ` Segher Boessenkool
2007-01-13  5:01   ` Adrian Bunk
2007-01-13 13:02     ` Jan Engelhardt
2007-01-14  7:38       ` Jeff Chua
2007-01-14  7:43         ` Adrian Bunk
2007-01-13  7:11 ` 2.6.20-rc5: known unfixed regressions Adrian Bunk
2007-01-13 15:51   ` Damien Wyart
2007-01-13 15:59     ` Adrian Bunk
2007-01-13 16:38       ` Jon Smirl
2007-01-13 20:55       ` Aaron Sethman
2007-01-14 12:09     ` Ingo Molnar
2007-01-16  6:15   ` David Chinner
2007-01-17  3:43     ` David Chinner
2007-01-18 22:55       ` Sami Farin
2007-01-13  7:14 ` 2.6.20-rc5: known regressions with patches Adrian Bunk
2007-01-13 15:32   ` Roland Dreier
2007-01-13 16:21     ` Adrian Bunk
2007-01-18 19:47 ` 2.6.20-rc5: knwon unfixed regressions (v2) (part1) Adrian Bunk
2007-01-18 19:54 ` 2.6.20-rc5: knwon unfixed regressions (v2) (part2) Adrian Bunk
2007-01-18 19:59 ` 2.6.20-rc5: known regressions with patches (v2) Adrian Bunk
2007-01-19  1:43   ` David Woodhouse
2007-01-24 15:46 ` 2.6.20-rc5: known unfixed regressions (v3) (part 1) Adrian Bunk
2007-01-24 15:47 ` 2.6.20-rc5: known unfixed regressions (v3) (part 2) Adrian Bunk
2007-01-24 16:06   ` Lennart Sorensen
2007-01-24 16:38     ` Adrian Bunk
2007-01-24 16:57       ` Lennart Sorensen [this message]
2007-01-24 20:06         ` Adrian Bunk
2007-01-24 20:45   ` Peter Osterlund
2007-01-25 15:32     ` Gerhard Dirschl
2007-01-26 11:13   ` Andrew Clayton
2007-01-24 15:50 ` 2.6.20-rc5: known regressions with patches (v3) Adrian Bunk

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=20070124165708.GF7582@csclub.uwaterloo.ca \
    --to=lsorense@csclub.uwaterloo.ca \
    --cc=akpm@osdl.org \
    --cc=bunk@stusta.de \
    --cc=jordan.crouse@amd.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=takada@mbf.nifty.com \
    --cc=torvalds@osdl.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;
as well as URLs for NNTP newsgroup(s).