From: Ben Hutchings <bhutchings@solarflare.com>
To: Andy Fleming <afleming@freescale.com>
Cc: netdev@vger.kernel.org, ncase@xes-inc.com
Subject: Re: [RFC] Change mii_bus id field to a string
Date: Thu, 3 Apr 2008 20:26:04 +0100 [thread overview]
Message-ID: <20080403192603.GM21637@solarflare.com> (raw)
In-Reply-To: <1207176592-4224-1-git-send-email-afleming@freescale.com>
Andy Fleming wrote:
> diff --git a/include/linux/phy.h b/include/linux/phy.h
> index 5e43ae7..92a4829 100644
> --- a/include/linux/phy.h
> +++ b/include/linux/phy.h
> @@ -63,8 +63,6 @@ typedef enum {
> PHY_INTERFACE_MODE_RTBI
> } phy_interface_t;
>
> -#define MII_BUS_MAX 4
> -
>
> #define PHY_INIT_TIMEOUT 100000
> #define PHY_STATE_TIME 1
> @@ -74,20 +72,30 @@ typedef enum {
> #define PHY_MAX_ADDR 32
>
> /* Used when trying to connect to a specific phy (mii bus id:phy device id) */
> -#define PHY_ID_FMT "%x:%02x"
> +#define PHY_ID_FMT "%s:%02x"
> +
> +/*
> + * Need to be a little smaller than phydev->dev.bus_id to leave room
> + * for the ":%02x"
> + */
> +#define MII_BUS_ID_SIZE BUS_ID_SIZE - 3
The macro's definition should be parenthesised.
>
> -/* The Bus class for PHYs. Devices which provide access to
> - * PHYs should register using this structure */
> +/*
> + * The Bus class for PHYs. Devices which provide access to
> + * PHYs should register using this structure
> + */
I'm not sure why you reformatted this and other comments. If you really
think it's necessary to do that, you should probably post a separate patch
rather than combining it with this functional change.
Ben.
--
Ben Hutchings, Senior Software Engineer, Solarflare Communications
Not speaking for my employer; that's the marketing department's job.
next prev parent reply other threads:[~2008-04-03 19:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-02 22:49 [RFC] Change mii_bus id field to a string Andy Fleming
2008-04-03 19:26 ` Ben Hutchings [this message]
2008-04-03 20:19 ` Andy Fleming
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=20080403192603.GM21637@solarflare.com \
--to=bhutchings@solarflare.com \
--cc=afleming@freescale.com \
--cc=ncase@xes-inc.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).