[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <9372d46f-d1c9-a9c5-e689-54cd7f3ef930@cumulusnetworks.com>
Date: Tue, 28 Nov 2017 09:05:36 -0700
From: David Ahern <dsa@...ulusnetworks.com>
To: Jiri Pirko <jiri@...nulli.us>
Cc: Arkadi Sharshevsky <arkadis@...lanox.com>, netdev@...r.kernel.org,
davem@...emloft.net, mlxsw@...lanox.com, andrew@...n.ch,
vivien.didelot@...oirfairelinux.com, f.fainelli@...il.com,
michael.chan@...adcom.com, ganeshgr@...lsio.com,
saeedm@...lanox.com, matanb@...lanox.com, leonro@...lanox.com,
idosch@...lanox.com, jakub.kicinski@...ronome.com, ast@...nel.org,
daniel@...earbox.net, simon.horman@...ronome.com,
pieter.jansenvanvuuren@...ronome.com, john.hurley@...ronome.com,
alexander.h.duyck@...el.com, linville@...driver.com,
gospo@...adcom.com, steven.lin1@...adcom.com, yuvalm@...lanox.com,
ogerlitz@...lanox.com, roopa@...ulusnetworks.com
Subject: Re: [patch net-next RFC v2 08/11] mlxsw: spectrum_dpipe: Connect
dpipe tables to resources
On 11/28/17 6:27 AM, Jiri Pirko wrote:
>
> I have to be missing something. You can easily see the relation between
> each dpipe table and resources already as a part of this patchset. The
> string you suggest shows the same thing, therefore it is completely
> redundant. What am I missing?
>
At this point let's see a working RFC v3 and we can discuss from there.
Powered by blists - more mailing lists