public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn•ch>
To: Florian Fainelli <f.fainelli@gmail•com>
Cc: netdev@vger•kernel.org, davem@davemloft•net
Subject: Re: [PATCH net-next 3/3] net: sysfs: Document PHY device sysfs attributes
Date: Wed, 24 May 2017 22:10:18 +0200	[thread overview]
Message-ID: <20170524201018.GH1788@lunn.ch> (raw)
In-Reply-To: <20170524193354.10739-4-f.fainelli@gmail.com>

> +What:		/sys/class/mdio_bus/<bus>/<device>/phy_interface
> +Date:		February 2014
> +KernelVersion:	3.15
> +Contact:	netdev@vger•kernel.org
> +Description:
> +		String value indicating the PHY interface, possible
> +		values are in include/linux/phy.h function phy_modes.

Hi Florian

Does this suggest that these strings should be moved to
include/uapi/linux/phy.h?

	Andrew

  reply	other threads:[~2017-05-24 20:10 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-24 19:33 [PATCH net-next 0/3] net: phy: Create sysfs reciprocal links for attached_dev/phydev Florian Fainelli
2017-05-24 19:33 ` [PATCH net-next 1/3] " Florian Fainelli
2017-05-26 23:34   ` Woojung.Huh
2017-05-26 23:44     ` Florian Fainelli
2017-05-26 23:52       ` Woojung.Huh
2017-05-27  0:02         ` Florian Fainelli
2017-05-27  0:20           ` Woojung.Huh
2017-05-27  0:33             ` Florian Fainelli
2017-05-27  0:43               ` Woojung.Huh
2017-05-27  0:46                 ` Florian Fainelli
2017-05-27  1:00                   ` Woojung.Huh
2017-05-27  1:26                     ` Florian Fainelli
2017-05-27  1:31                       ` Woojung.Huh
2017-05-27  3:22                         ` Florian Fainelli
2017-05-24 19:33 ` [PATCH net-next 2/3] net: sysfs: Document "phydev" symbolic link Florian Fainelli
2017-05-24 19:33 ` [PATCH net-next 3/3] net: sysfs: Document PHY device sysfs attributes Florian Fainelli
2017-05-24 20:10   ` Andrew Lunn [this message]
2017-05-24 23:07     ` Florian Fainelli
2017-05-25  0:03       ` 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=20170524201018.GH1788@lunn.ch \
    --to=andrew@lunn$(echo .)ch \
    --cc=davem@davemloft$(echo .)net \
    --cc=f.fainelli@gmail$(echo .)com \
    --cc=netdev@vger$(echo .)kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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