From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Andreas Herrmann <aherrman@arcor.de>
Cc: linux-fbdev-devel@lists.sourceforge.net
Subject: Re: [PATCH] radeonfb: add chip definition for RV370 5b63
Date: Fri, 16 Nov 2007 10:31:31 +1100 [thread overview]
Message-ID: <1195169491.28865.108.camel@pasglop> (raw)
In-Reply-To: <20071116002017.GA11518@devil>
On Fri, 2007-11-16 at 01:20 +0100, Andreas Herrmann wrote:
> .. which I've found on a Sapphire X550 (Silent).
>
> Signed-off-by: Andreas Herrmann <aherrman@arcor.de>
> ---
If it works, go for it. Ack.
Ben.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
prev parent reply other threads:[~2007-11-15 23:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-16 0:20 [PATCH] radeonfb: add chip definition for RV370 5b63 Andreas Herrmann
2007-11-15 23:31 ` Benjamin Herrenschmidt [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=1195169491.28865.108.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=aherrman@arcor.de \
--cc=linux-fbdev-devel@lists.sourceforge.net \
/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).