[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190825060810.181f65c9@nic.cz>
Date: Sun, 25 Aug 2019 06:08:10 +0200
From: Marek Behun <marek.behun@....cz>
To: Florian Fainelli <f.fainelli@...il.com>
Cc: netdev@...r.kernel.org, Andrew Lunn <andrew@...n.ch>,
Vivien Didelot <vivien.didelot@...il.com>,
David Ahern <dsahern@...il.com>,
Stephen Hemminger <stephen@...workplumber.org>,
Chris Healy <cphealy@...il.com>,
Vladimir Oltean <olteanv@...il.com>
Subject: Re: [PATCH RFC net-next 0/3] Multi-CPU DSA support
On Sat, 24 Aug 2019 23:01:21 +0200
Marek Behun <marek.behun@....cz> wrote:
> the documentation would became weird to users.
... would become weird ...
>
> We are *already* using the iflink property to report which CPU device
> is used as CPU destination port for a given switch slave interface. So
> why to use that for changing this, also?
... why NOT to use that for chaning this also?
>
> If you think that iflink should not be used for this, and other agree,
... and others agree with you,
Powered by blists - more mailing lists