From: Florian Fainelli <f.fainelli@gmail.com>
To: Dan Williams <dcbw@redhat.com>, netdev@vger.kernel.org
Cc: Joshua Watt <jpewdev@gmail.com>, jpirko@redhat.com
Subject: Re: [PATCH] Documentation: clarify phys_port_id
Date: Wed, 17 Dec 2014 15:24:51 -0800 [thread overview]
Message-ID: <549210C3.7010606@gmail.com> (raw)
In-Reply-To: <1418835576.1160.38.camel@dcbw.local>
On 17/12/14 08:59, Dan Williams wrote:
> Signed-off-by: Dan Williams <dcbw@redhat.com>
Reviewed-by: Florian Fainelli <f.fainelli@gmail.com>
> ---
> Documentation/ABI/testing/sysfs-class-net | 7 ++++++-
> 1 file changed, 6 insertions(+), 1 deletion(-)
>
> diff --git a/Documentation/ABI/testing/sysfs-class-net b/Documentation/ABI/testing/sysfs-class-net
> index e1b2e78..7fe823a 100644
> --- a/Documentation/ABI/testing/sysfs-class-net
> +++ b/Documentation/ABI/testing/sysfs-class-net
> @@ -186,7 +186,12 @@ KernelVersion: 3.12
> Contact: netdev@vger.kernel.org
> Description:
> Indicates the interface unique physical port identifier within
> - the NIC, as a string.
> + the NIC, as a string. If two net_device objects share physical
> + hardware or other resources, and/or do not operate independently
> + both net_device objects should be assigned the
> + same phys_port_id. phys_port_id should be as globally unique
> + as possible to prevent conflicts between different drivers and
> + vendors, eg with MAC addresses or hardware GUIDs.
>
> What: /sys/class/net/<iface>/speed
> Date: October 2009
>
next prev parent reply other threads:[~2014-12-17 23:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-17 16:09 Question about phys_port_id Joshua Watt
2014-12-17 16:47 ` Dan Williams
2014-12-17 16:59 ` [PATCH] Documentation: clarify phys_port_id Dan Williams
2014-12-17 23:24 ` Florian Fainelli [this message]
2014-12-18 5:57 ` Sathya Perla
2014-12-18 15:35 ` Dan Williams
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=549210C3.7010606@gmail.com \
--to=f.fainelli@gmail.com \
--cc=dcbw@redhat.com \
--cc=jpewdev@gmail.com \
--cc=jpirko@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.