From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: James Simmons <jsimmons@infradead.org>
Cc: Kronos <kronos@kronoz.cjb.net>,
Linux Fbdev development list
<linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: Re: [PATCH] Fix get_std_timing
Date: Fri, 05 Mar 2004 13:37:30 +1100 [thread overview]
Message-ID: <1078454250.6327.47.camel@gaston> (raw)
In-Reply-To: <Pine.LNX.4.44.0403042230440.13104-100000@phoenix.infradead.org>
On Fri, 2004-03-05 at 09:31, James Simmons wrote:
> Ug. I applied the fix. I will be pushing the new monitor code as soon as
> ben sends me bugs he found as well.
I don't have anything with the fbmon at this point. The problems I
have are local to radeonfb, you can go & push that update
Ben.
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
next prev parent reply other threads:[~2004-03-05 2:52 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-04 22:15 [PATCH] Fix get_std_timing Kronos
2004-03-04 22:31 ` James Simmons
2004-03-05 2:37 ` Benjamin Herrenschmidt [this message]
2004-03-11 17:43 ` James Simmons
2004-03-11 17:50 ` Andrew Morton
2004-03-11 18:06 ` James Simmons
2004-03-11 18:13 ` Andrew Morton
2004-03-11 18:20 ` James Simmons
2004-03-11 22:49 ` Benjamin Herrenschmidt
2004-03-11 23:31 ` James Simmons
2004-03-12 23:46 ` character drawing enhancement James Simmons
2004-03-11 18:23 ` Re: [PATCH] Fix get_std_timing James Simmons
2004-03-11 22:48 ` Benjamin Herrenschmidt
2004-03-11 23:26 ` James Simmons
2004-03-11 18:29 ` Kronos
2004-03-11 19:32 ` James Simmons
2004-03-11 22:46 ` Benjamin Herrenschmidt
2004-03-11 23:32 ` James Simmons
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=1078454250.6327.47.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=jsimmons@infradead.org \
--cc=kronos@kronoz.cjb.net \
--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).