From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Samuel Rydh <samuel@ibrium.se>
Cc: linuxppc-dev list <linuxppc-dev@lists.linuxppc.org>
Subject: Re: [PATCH] radeonfb fix
Date: Sun, 04 Jan 2004 10:00:30 +1100 [thread overview]
Message-ID: <1073170830.10542.41.camel@gaston> (raw)
In-Reply-To: <20040103183242.GB1309@ibrium.se>
On Sun, 2004-01-04 at 05:32, Samuel Rydh wrote:
> Hi,
>
> The following patch is necessary to get the 2.6 radeonfb driver to detect
> the flatpanel display. I believe the 2.4 code does exactly the same thing.
Could you verify that the "new" radeonfb driver in my tree works
fine for you ? I rewrote significant parts of this driver, I expect
to have it merged upstream soon now.
Ben.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-01-03 23:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-03 18:32 [PATCH] radeonfb fix Samuel Rydh
2004-01-03 23:00 ` Benjamin Herrenschmidt [this message]
2004-01-04 14:05 ` Samuel Rydh
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=1073170830.10542.41.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=samuel@ibrium.se \
/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).