All of lore.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: "David S. Miller" <davem@redhat.com>
Cc: Jeff Garzik <jgarzik@pobox.com>,
	Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] sungem: add support for G5 PowerMac, some PM fixes
Date: Mon, 26 Jan 2004 18:13:53 +1100	[thread overview]
Message-ID: <1075101232.5659.19.camel@gaston> (raw)
In-Reply-To: <20040125.230102.71560587.davem@redhat.com>

On Mon, 2004-01-26 at 18:01, David S. Miller wrote:
>    From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
>    Date: Fri, 23 Jan 2004 10:13:12 +1100
> 
>    Anyway, here's the fixed version.
> 
> Applied, thanks.  This one might have to wait for 2.6.3-pre1 though
> for merging.

That's fine, the rest of the PowerMac updates are waiting for 2.6.3 too.
>    The 2.4 backport will come next week hopefully when I'll walk
>    through all my pending 2.4 stuffs, I want to dbl check a few things
>    in it first (and I'm not yet 100% certain I will merge the G5
>    support in 2.4 upstream anyway).
> 
> You should be able to literally copy the 2.6.x driver into the 2.4.x
> tree with perhaps only a one liner or two (if that).

Yes. I'll do that along with other things I need to backport.

>    the new PCI ID isn't yet in Linus tree, but it's in the patches
>    I'm currently sending to Andrew.
> 
> I'd prefer in the future you not do it this way, just give it
> instead within the driver update so that you patch by itself
> stands alone.

Ok.

Ben.



      reply	other threads:[~2004-01-26  7:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-22  5:50 [PATCH] sungem: add support for G5 PowerMac, some PM fixes Benjamin Herrenschmidt
2004-01-22  6:08 ` David S. Miller
2004-01-22 23:13   ` Benjamin Herrenschmidt
2004-01-26  7:01     ` David S. Miller
2004-01-26  7:13       ` 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=1075101232.5659.19.camel@gaston \
    --to=benh@kernel.crashing.org \
    --cc=davem@redhat.com \
    --cc=jgarzik@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.