From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: linux-fbdev-devel@lists.sourceforge.net
Cc: "Antonino A. Daplas" <adaplas@hotpop.com>, Andrew Morton <akpm@osdl.org>
Subject: Re: [PATCH] nvidiafb: Fix 6xxx/7xxx cards
Date: Mon, 09 Jan 2006 13:32:13 +1100 [thread overview]
Message-ID: <1136773933.30123.100.camel@localhost.localdomain> (raw)
In-Reply-To: <1134287682.6989.49.camel@gaston>
On Sun, 2005-12-11 at 18:54 +1100, Benjamin Herrenschmidt wrote:
> > I already told akpm to drop mine and take yours instead as you already
> > verified that it works. I'll send you the pci-e support patch, diffed
> > against your patch if you want.
It's not yet upstream and we are about to merge the new g5 support.
Andrew, will you send it to Linus or was there some issues with the
patch ?
Ben.
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
next prev parent reply other threads:[~2006-01-09 2:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-07 8:33 [PATCH] nvidiafb: Fix 6xxx/7xxx cards Benjamin Herrenschmidt
2005-12-08 20:54 ` Antonino A. Daplas
2005-12-08 22:17 ` Benjamin Herrenschmidt
2005-12-08 22:54 ` Antonino A. Daplas
2005-12-11 7:54 ` Benjamin Herrenschmidt
2006-01-09 2:32 ` Benjamin Herrenschmidt [this message]
2006-01-09 3:13 ` Andrew Morton
2006-01-09 4:13 ` Benjamin Herrenschmidt
2006-01-09 5:43 ` Andrew Morton
2006-01-09 6:38 ` Benjamin Herrenschmidt
2006-01-10 1:23 ` Antonino A. Daplas
2006-01-10 1:26 ` Antonino A. Daplas
2006-01-10 2:35 ` Benjamin Herrenschmidt
2006-01-10 3:08 ` Andrew Morton
2006-01-10 3:23 ` Benjamin Herrenschmidt
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=1136773933.30123.100.camel@localhost.localdomain \
--to=benh@kernel.crashing.org \
--cc=adaplas@hotpop.com \
--cc=akpm@osdl.org \
--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).