netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: Paul Gortmaker <paul.gortmaker@windriver.com>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH] PHY: add BCM5464 support to broadcom PHY driver
Date: Wed, 16 Apr 2008 20:54:26 -0400	[thread overview]
Message-ID: <48069FC2.60900@garzik.org> (raw)
In-Reply-To: <20080415033538.GA14095@windriver.com>

Paul Gortmaker wrote:
> In message: Re: [PATCH] PHY: add BCM5464 support to broadcom PHY driver
> on 12/04/2008 Jeff Garzik wrote:
> 
>> doesn't seem to apply...  can you please regenerate against  
>> git://git.kernel.org/pub/scm/linux/kernel/git/davem/net-2.6.26.git ?
> 
> No problem.  The already queued BCM 5481 and this overlapped. It should
> be good to go now.
> 
> P.
> ---
> 
>  From f01cb20f9d5c4f6cc9040c0a5ec13409396e64d5 Mon Sep 17 00:00:00 2001
> From: Paul Gortmaker <paul.gortmaker@windriver.com>
> Date: Mon, 14 Apr 2008 23:27:12 -0400
> Subject: [PATCH] PHY: add BCM5464 support to broadcom PHY driver
> 
> The BCM5464 can be used with the current broadcom PHY driver
> by just adding the appropriate chip ID and using the existing
> support within.
> 
> Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>
> ---
>  drivers/net/phy/broadcom.c |   20 ++++++++++++++++++++
>  1 files changed, 20 insertions(+), 0 deletions(-)

applied



      reply	other threads:[~2008-04-17  0:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1207752406-4624-1-git-send-email-paul.gortmaker@windriver.com>
     [not found] ` <20080409150412.GA4912@windriver.com>
     [not found]   ` <48007C3F.5050505@garzik.org>
2008-04-15  3:35     ` [PATCH] PHY: add BCM5464 support to broadcom PHY driver Paul Gortmaker
2008-04-17  0:54       ` Jeff Garzik [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=48069FC2.60900@garzik.org \
    --to=jeff@garzik.org \
    --cc=netdev@vger.kernel.org \
    --cc=paul.gortmaker@windriver.com \
    /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).