All of lore.kernel.org
 help / color / mirror / Atom feed
From: Florian Fainelli <f.fainelli@gmail.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: David Miller <davem@davemloft.net>,
	netdev <netdev@vger.kernel.org>,
	sfrench@samba.org, linux-cifs@vger.kernel.org,
	Vivien Didelot <vivien.didelot@savoirfairelinux.com>
Subject: Re: [PATCH net-next 2/2] net: dsa: dsa2: Add basic support of devlink
Date: Wed, 29 Mar 2017 10:29:07 -0700	[thread overview]
Message-ID: <c844a885-cfd3-4358-89dd-c619d3d394e4@gmail.com> (raw)
In-Reply-To: <20170329013112.GF3152@lunn.ch>

On 03/28/2017 06:31 PM, Andrew Lunn wrote:
> On Tue, Mar 28, 2017 at 05:33:18PM -0700, Florian Fainelli wrote:
>> On 03/28/2017 02:45 PM, Andrew Lunn wrote:
>>> Register the switch and its ports with devlink.
>>>
>>> Signed-off-by: Andrew Lunn <andrew@lunn.ch>
>>
>> Reviewed-by: Florian Fainelli <f.fainelli@gmail.com>
>> Tested-by: Florian Fainelli <f.fainelli@gmail.com>
>>
>> root@net-vm:~# devlink -p port
>> mdio_bus/fixed-0:1f/0: type eth netdev lan1
>> mdio_bus/fixed-0:1f/1: type eth netdev lan2
>> mdio_bus/fixed-0:1f/2: type eth netdev lan3
>> mdio_bus/fixed-0:1f/3: type eth netdev lan4
>> mdio_bus/fixed-0:1f/5: type notset
>> root@net-vm:~# devlink -p dev
>> mdio_bus/fixed-0:1f
> 
> Thanks Florian
> 
> I have another patch somewhere which adds new types for CPU and DSA
> ports. Once these 2 patches have landed, and the reports of broken
> builds stop, i will dig it out.
> 
> But my main priority at the moment is to play with dpipe and make sure
> it can represent tables we have in DSA switches, before the Binary API
> is frozen.

Yes, that is a very good point actually.

Tangential question: we do not currently report to user space what kind
of switch tagging protocol is used (DSA, eDSA etc.) I was going to add a
sysfs attribute for that under the switch device's directory, but maybe
devlink would be more appropriate for that?
-- 
Florian

  reply	other threads:[~2017-03-29 17:29 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-28 21:45 [PATCH net-next 0/2] break include loop and dsa devlink support Andrew Lunn
     [not found] ` <1490737507-7864-1-git-send-email-andrew-g2DYL2Zd6BY@public.gmane.org>
2017-03-28 21:45   ` [PATCH net-next 1/2] net: break include loop netdevice.h, dsa.h, devlink.h Andrew Lunn
     [not found]     ` <1490737507-7864-2-git-send-email-andrew-g2DYL2Zd6BY@public.gmane.org>
2017-03-28 22:04       ` Florian Fainelli
2017-03-29  5:46   ` [PATCH net-next 0/2] break include loop and dsa devlink support David Miller
2017-03-28 21:45 ` [PATCH net-next 2/2] net: dsa: dsa2: Add basic support of devlink Andrew Lunn
2017-03-29  0:33   ` Florian Fainelli
     [not found]     ` <2fe7ffc9-1bf1-537a-e361-33156a6f5a07-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-03-29  1:31       ` Andrew Lunn
2017-03-29 17:29         ` Florian Fainelli [this message]
     [not found]           ` <c844a885-cfd3-4358-89dd-c619d3d394e4-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-03-29 17:36             ` Andrew Lunn
2017-03-30  6:17               ` Jiri Pirko

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=c844a885-cfd3-4358-89dd-c619d3d394e4@gmail.com \
    --to=f.fainelli@gmail.com \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=linux-cifs@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=sfrench@samba.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 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.