linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: linux-fbdev-devel@lists.sourceforge.net
Cc: benh@kernel.crashing.org, adaplas@hotpop.com
Subject: Re: [PATCH] nvidiafb: Fix 6xxx/7xxx cards
Date: Sun, 8 Jan 2006 19:13:11 -0800	[thread overview]
Message-ID: <20060108191311.00ab5dba.akpm@osdl.org> (raw)
In-Reply-To: <1136773933.30123.100.camel@localhost.localdomain>

Benjamin Herrenschmidt <benh@kernel.crashing.org> wrote:
>
> 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 didn't get that message..

>  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 ?
> 

Current nvidia patches which I have are:

nvidiafb-i2c-bus-name-beautification.patch
fbdev-nvidiafb-driver-cleanup.patch
nvidiafb-add-support-for-some-pci-e-chipsets.patch
nvidiafb-add-support-for-some-pci-e-chipsets-fix.patch
nvidiafb-add-boot-option-bpp.patch
nvidiafb-reduce-stack-usage.patch
nvidia-agp-use-time_before_eq.patch

None of those appear to do the same thing as Ben's patch, so I don't know
what's going on here.


Gad.  It looks like a variant of Ben's patch is in the powerpc tree.  wtf
is it doing there?


Anyway, all of the above patches apply OK to whatever is in git-powerpc so
I spose we can just merge git-powerpc and be happy.  Soon, I hope - I have
a few things held up by that tree.

Tell Paul to grovel appropriately to Linus when he sends it though -
putting non-arch stuff into an arch tree tends to upset him.  


-------------------------------------------------------
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

  reply	other threads:[~2006-01-09  3:17 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
2006-01-09  3:13           ` Andrew Morton [this message]
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=20060108191311.00ab5dba.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=adaplas@hotpop.com \
    --cc=benh@kernel.crashing.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).