From: Hauke Mehrtens <hauke@hauke-m.de>
To: davem@davemloft.net
Cc: mcarlson@broadcom.com, mchan@broadcom.com,
netdev@vger.kernel.org, m@bues.ch
Subject: Re: [PATCH 0/3] tg3: add support for Ethernet core in BCM4785
Date: Thu, 24 Jan 2013 18:21:09 +0100 [thread overview]
Message-ID: <51016D85.8030705@hauke-m.de> (raw)
In-Reply-To: <1358020905-9924-1-git-send-email-hauke@hauke-m.de>
On 01/12/2013 09:01 PM, Hauke Mehrtens wrote:
> These patches are adding support for the Ethernet core found in the BCM4705/BCM4785 SoC.
>
> Hauke Mehrtens (3):
> ssb: add missing method ssb_gige_get_macaddr
> tg3: make it possible to provide phy_id in ioctl
> tg3: add support for Ethernet core in bcm4785
>
> drivers/net/ethernet/broadcom/tg3.c | 137 +++++++++++++++++++++++++++++++----
> drivers/net/ethernet/broadcom/tg3.h | 5 ++
> include/linux/pci_ids.h | 1 +
> include/linux/ssb/ssb_driver_gige.h | 3 +
> 4 files changed, 133 insertions(+), 13 deletions(-)
>
Hi David,
Should I resend these patches with error handling if the mac address
could not be set?
Hauke
prev parent reply other threads:[~2013-01-24 17:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-12 20:01 [PATCH 0/3] tg3: add support for Ethernet core in BCM4785 Hauke Mehrtens
2013-01-12 20:01 ` [PATCH 1/3] ssb: add missing method ssb_gige_get_macaddr Hauke Mehrtens
2013-01-12 23:32 ` David Miller
2013-01-13 9:47 ` Michael Büsch
2013-01-13 22:31 ` Hauke Mehrtens
2013-01-12 20:01 ` [PATCH 2/3] tg3: make it possible to provide phy_id in ioctl Hauke Mehrtens
2013-01-12 20:01 ` [PATCH 3/3] tg3: add support for Ethernet core in bcm4785 Hauke Mehrtens
2013-01-12 23:32 ` [PATCH 0/3] tg3: add support for Ethernet core in BCM4785 David Miller
2013-01-13 22:26 ` Hauke Mehrtens
2013-01-24 17:21 ` Hauke Mehrtens [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=51016D85.8030705@hauke-m.de \
--to=hauke@hauke-m.de \
--cc=davem@davemloft.net \
--cc=m@bues.ch \
--cc=mcarlson@broadcom.com \
--cc=mchan@broadcom.com \
--cc=netdev@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 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).