All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jordan Crouse" <jordan.crouse@amd.com>
To: "Andres Salomon" <dilinger@queued.net>
Cc: "Thomas Gleixner" <tglx@linutronix.de>,
	linux-kernel@vger.kernel.org, info-linux@geode.amd.com,
	mingo@redhat.com, hpa@zytor.com, akpm@linux-foundation.org
Subject: Re: x86: geode: MSR cleanup
Date: Mon, 25 Feb 2008 08:52:55 -0700	[thread overview]
Message-ID: <20080225155255.GE13031@cosmic.amd.com> (raw)
In-Reply-To: <20080224183300.037fa9c8@ephemeral>

On 24/02/08 18:33 -0500, Andres Salomon wrote:
> Note that I didn't bother cleaning up the gxfb and lxfb headers wrt MSRs;
> that's coming in another patch (which is still in progress).
> 
> 
> From 22b8ddf47f77f01a59afb937779f4c83e9862f9e Mon Sep 17 00:00:00 2001
> From: Andres Salomon <dilinger@debian.org>
> Date: Sun, 24 Feb 2008 13:14:57 -0500
> Subject: [PATCH] x86: geode: MSR cleanup
> 
> This cleans up a few MSR-using drivers in the following manner:
>   - Ensures MSRs are all defined in asm/geode.h, rather than in misc
>     places
>   - Makes the naming consistent; cs553[56] ones begin with MSR_,
>     GX-specific ones start with MSR_GX_, and LX-specific ones start
>     with MSR_LX_.  Also, make the names match the data sheet.
>   - Use MSR names rather than numbers in source code
>   - Document the fact that the LX's MSR_PADSEL has the wrong value
>     in the data sheet.  That's, uh, good to note.
> 
> Signed-off-by: Andres Salomon <dilinger@debian.org>

Acked-by: Jordan Crouse <jordan.crouse@amd.com>

Thanks for doing this - I'm always happy when stuff gets scratched off my
TODO list automatically.



      reply	other threads:[~2008-02-25 15:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-24 23:33 [PATCH] x86: geode: MSR cleanup Andres Salomon
2008-02-25 15:52 ` Jordan Crouse [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=20080225155255.GE13031@cosmic.amd.com \
    --to=jordan.crouse@amd.com \
    --cc=akpm@linux-foundation.org \
    --cc=dilinger@queued.net \
    --cc=hpa@zytor.com \
    --cc=info-linux@geode.amd.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    /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.