From: Andres Salomon <dilinger@queued.net>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: jordan.crouse@amd.com, linux-fbdev-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org, adaplas@gmail.com,
info-linux@geode.amd.com
Subject: Re: [PATCH 3/6] gxfb: move MSR bit fields into gxfb.h
Date: Mon, 10 Mar 2008 16:28:44 -0400 [thread overview]
Message-ID: <20080310162844.6e8e9215@ephemeral> (raw)
In-Reply-To: <20080310131432.e4567537.akpm@linux-foundation.org>
On Mon, 10 Mar 2008 13:14:32 -0700
Andrew Morton <akpm@linux-foundation.org> wrote:
> On Sat, 8 Mar 2008 20:48:40 -0500
> Andres Salomon <dilinger@queued.net> wrote:
>
> > >From bee7242cf04c4a060b311b11985efb495f308355 Mon Sep 17 00:00:00 2001
> > From: Andres Salomon <dilinger@debian.org>
> > Date: Mon, 25 Feb 2008 15:29:36 -0500
> > Subject: [PATCH] gxfb: move MSR bit fields into gxfb.h
> >
> > This continues the gxfb header cleanups. MSRs are defined in geode.h;
> > the specific bits we care about are defined in gxfb.h.
> >
> > Signed-off-by: Andres Salomon <dilinger@debian.org>
> > ---
> > drivers/video/geode/display_gx.h | 3 ---
> > drivers/video/geode/gxfb.h | 16 ++++++++++++++++
> > drivers/video/geode/gxfb_core.c | 2 +-
> > drivers/video/geode/video_gx.c | 4 ++--
> > drivers/video/geode/video_gx.h | 14 --------------
> > 5 files changed, 19 insertions(+), 20 deletions(-)
> >
> > diff --git a/drivers/video/geode/display_gx.h b/drivers/video/geode/display_gx.h
> > index 56e9d2e..ad556d3 100644
> > --- a/drivers/video/geode/display_gx.h
> > +++ b/drivers/video/geode/display_gx.h
> > @@ -16,7 +16,4 @@ int gx_line_delta(int xres, int bpp);
> >
> > extern struct geode_dc_ops gx_dc_ops;
> >
> > -/* MSR that tells us if a TFT or CRT is attached */
> > -#define GLD_MSR_CONFIG_DM_FP 0x40
> > -
> > #endif /* !__DISPLAY_GX1_H__ */
>
> Something has gone wrong here. The code in current mainline is
>
>
>
> extern struct geode_dc_ops gx_dc_ops;
>
> /* MSR that tells us if a TFT or CRT is attached */
> #define GLD_MSR_CONFIG 0xC0002001
> #define GLD_MSR_CONFIG_DM_FP 0x40
>
> /* Display controller registers */
>
>
> whereas you're patching something else.
>
>
> In [1/6] you refer to "the MSR cleanup patch". I don't know what that is.
>
That would be this:
http://thread.gmane.org/gmane.linux.kernel/645387/focus=645636
>
> Please clean up the changelogs - remove those email headers from the
> email-forwarding operation and remove the additional little commentary on
> top: if there's actually anything in there which is needed then it should
> be integrated into the changelog proper, thanks.
>
For future requests, or should I resend these to you?
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
next prev parent reply other threads:[~2008-03-10 20:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-09 1:48 [PATCH 3/6] gxfb: move MSR bit fields into gxfb.h Andres Salomon
2008-03-10 20:14 ` Andrew Morton
2008-03-10 20:28 ` Andres Salomon [this message]
2008-03-10 21:26 ` Andrew Morton
-- strict thread matches above, loose matches on Subject: below --
2008-03-11 22:14 Andres Salomon
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=20080310162844.6e8e9215@ephemeral \
--to=dilinger@queued.net \
--cc=adaplas@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=info-linux@geode.amd.com \
--cc=jordan.crouse@amd.com \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.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).