From: Greg KH <gregkh@suse.de>
To: David Miller <davem@davemloft.net>
Cc: ddaney@caviumnetworks.com, ralf@linux-mips.org,
linux-mips@linux-mips.org, netdev@vger.kernel.org
Subject: Re: [PATCH 0/2] Fix ethernet driver for Octeon based Movidis hardware
Date: Fri, 2 Apr 2010 10:04:24 -0700 [thread overview]
Message-ID: <20100402170424.GC32293@suse.de> (raw)
In-Reply-To: <20100401.182045.106908204.davem@davemloft.net>
On Thu, Apr 01, 2010 at 06:20:45PM -0700, David Miller wrote:
> From: David Daney <ddaney@caviumnetworks.com>
> Date: Thu, 1 Apr 2010 18:17:53 -0700
>
> > The Movidis X16 bootloader doesn't enable the mdio bus. The first
> > patch fixes this by enabling the mdio bus when the driver is
> > initialized.
> >
> > Also the addresses of the PHYs was unknown for this device. The
> > second patch adds the corresponding PHY addresses.
> >
> > With both patches applied I can successfully use all eight Ethernet
> > ports.
> >
> > Please consider for 2.6.34. Since Octeon is an embedded MIPS SOC it
> > is unlikely to break the kernel for any workstations. Any or all of
> > these could be considered for merging via Ralf's linux-mips.org tree.
>
> Ralf please merge this via your MIPS tree, thanks:
>
> Acked-by: David S. Miller <davem@davemloft.net>
I agree, Ralf, please take these and you can add:
Acked-by: Greg Kroah-Hartman <gregkh@suse.de>
to them.
thanks,
greg k-h
prev parent reply other threads:[~2010-04-02 17:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-02 1:17 [PATCH 0/2] Fix ethernet driver for Octeon based Movidis hardware David Daney
2010-04-02 1:17 ` [PATCH 1/2] netdev: phy/mdio-octeon: Enable the hardware before using it David Daney
2010-04-02 1:17 ` [PATCH 2/2] staging: octeon-ethernet: Use proper phy addresses for Movidis hardware David Daney
2010-04-02 1:20 ` [PATCH 0/2] Fix ethernet driver for Octeon based " David Miller
2010-04-02 17:04 ` Greg KH [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=20100402170424.GC32293@suse.de \
--to=gregkh@suse.de \
--cc=davem@davemloft.net \
--cc=ddaney@caviumnetworks.com \
--cc=linux-mips@linux-mips.org \
--cc=netdev@vger.kernel.org \
--cc=ralf@linux-mips.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 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).