mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Egil Hjelmeland <egil.hjelmeland@zenitel.com>
To: Florian Fainelli <f.fainelli@gmail.com>, <corbet@lwn.net>,
	<andrew@lunn.ch>, <vivien.didelot@savoirfairelinux.com>,
	<davem@davemloft.net>, <kernel@pengutronix.de>,
	<linux-doc@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<netdev@vger.kernel.org>
Subject: Re: [PATCH 11/13] net: dsa: lan9303: Added "alr_dump" sysfs port attribute
Date: Tue, 25 Jul 2017 10:36:06 +0200	[thread overview]
Message-ID: <5efaa5f5-851b-418d-173b-837daa41307c@zenitel.com> (raw)
In-Reply-To: <e5a1cefd-1e26-3a24-2928-3fd7d970d8a6@gmail.com>

On 24. juli 2017 18:54, Florian Fainelli wrote:
> On 07/20/2017 01:49 AM, Egil Hjelmeland wrote:
>> Added read only file /sys/class/net/<port>/lan9303/alr_dump,
>> that output 168 first ALR entires.
>>
>> Currently "bridge fdb show" does not include the CPU port, while
>> "alr_dump" list all three ports per entry.
> 
> Agreed, and this is a limitation we would probably want to remove in the
> future, but duplicating what already exists with "bridge fdb show" into
> a sysfs node is a non-starter.

OK, I will keep this for my self then.

Egil


DISCLAIMER:
This e-mail may contain confidential and privileged material for the sole use of the intended recipient. Any review, use, distribution or disclosure by others is strictly prohibited. If you are not the intended recipient (or authorized to receive for the recipient), please contact the sender by reply e-mail and delete all copies of this message.

      reply	other threads:[~2017-07-25  8:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-20  8:49 Egil Hjelmeland
2017-07-24 16:54 ` Florian Fainelli
2017-07-25  8:36   ` Egil Hjelmeland [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=5efaa5f5-851b-418d-173b-837daa41307c@zenitel.com \
    --to=egil.hjelmeland@zenitel.com \
    --cc=andrew@lunn.ch \
    --cc=corbet@lwn.net \
    --cc=davem@davemloft.net \
    --cc=f.fainelli@gmail.com \
    --cc=kernel@pengutronix.de \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=vivien.didelot@savoirfairelinux.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

all inboxes | Powered by JetHome®