From: Ingo Molnar <mingo@elte.hu>
To: Jordan Crouse <jordan.crouse@amd.com>
Cc: linux-kernel@vger.kernel.org, tglx@linutronix.de,
mingo@redhat.com, linux-geode@lists.infradead.org
Subject: Re: [PATCH] geode: Add a VSA2 ID for General Software
Date: Thu, 19 Jun 2008 14:20:40 +0200 [thread overview]
Message-ID: <20080619122040.GG7640@elte.hu> (raw)
In-Reply-To: <20080618173438.GA9130@cosmic.amd.com>
* Jordan Crouse <jordan.crouse@amd.com> wrote:
> We have learned from bitter experience that one of the Geode BIOS
> vendors, General Software, uses a different ID for their VSA
> implementation then the canonical version from AMD & Insyde. This
> patch adds the ID to the have_geode_vsa2() check, and should make lxfb
> work again on many GSW platforms. If Linus is planning another -rcX
> revision it would be good to try and get this in, otherwise please
> schedule this for the stable series and 2.6.27.
applied to tip/x86/urgent. Thanks,
Ingo
prev parent reply other threads:[~2008-06-19 12:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-18 17:34 [PATCH] geode: Add a VSA2 ID for General Software Jordan Crouse
2008-06-19 12:20 ` Ingo Molnar [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=20080619122040.GG7640@elte.hu \
--to=mingo@elte.hu \
--cc=jordan.crouse@amd.com \
--cc=linux-geode@lists.infradead.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox