Netdev List
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Hauke Mehrtens <hauke@hauke-m.de>
Cc: zambrano@broadcom.com, netdev@vger.kernel.org,
	Florian Fainelli <florian@openwrt.org>
Subject: Re: [RFC] b44: use phylib
Date: Wed, 18 Sep 2013 08:19:05 -0700	[thread overview]
Message-ID: <1379517545.1787.20.camel@joe-AO722> (raw)
In-Reply-To: <1377298608-18016-1-git-send-email-hauke@hauke-m.de>

On Sat, 2013-08-24 at 00:56 +0200, Hauke Mehrtens wrote:
> This splits the driver into the mac and a phy driver. On routers where
> this driver is used we have a switch which implements a phy and can be
> controlled by a phy driver.

One more trivial note:

> diff --git a/drivers/net/ethernet/broadcom/b44.c b/drivers/net/ethernet/broadcom/b44.c
[]
> +static void b44_adjust_link(struct net_device *dev)
> +{
[]
> +	if (status_changed) {
> +		pr_info("%s: link %s", dev->name, phydev->link ?
> +			"UP" : "DOWN");
> +		if (phydev->link)
> +			pr_cont(" - %d/%s", phydev->speed,
> +			phydev->duplex == DUPLEX_FULL ? "full" : "half");
> +		pr_cont("\n");
> +	}

This bit would be better as:

	if (status_change) {
		if (phydev->link)
			netdev_info(dev, "link UP - %d/%s\n",
				    phydev->speed,
				    phydev->duplex == DUPLEX_FULL
				    ? "full" : "half");
		else
			netdev_info(dev, "link DOWN\n");
	}

so there's no possible interleaving by other
thread messages.

  parent reply	other threads:[~2013-09-18 15:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-23 22:56 [RFC] b44: use phylib Hauke Mehrtens
2013-08-23 23:10 ` Joe Perches
2013-08-24 14:32   ` Hauke Mehrtens
2013-09-18 15:00   ` Hauke Mehrtens
2013-09-18 15:03 ` Hauke Mehrtens
2013-09-18 15:19 ` Joe Perches [this message]
2013-09-18 15:29   ` Florian Fainelli

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=1379517545.1787.20.camel@joe-AO722 \
    --to=joe@perches.com \
    --cc=florian@openwrt.org \
    --cc=hauke@hauke-m.de \
    --cc=netdev@vger.kernel.org \
    --cc=zambrano@broadcom.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