From: Florian Fainelli <f.fainelli@gmail.com>
To: Vladimir Oltean <vladimir.oltean@nxp.com>
Cc: Andrew Lunn <andrew@lunn.ch>,
Stephen Hemminger <stephen@networkplumber.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
David Ahern <dsahern@kernel.org>,
Vivien Didelot <vivien.didelot@gmail.com>
Subject: Re: [PATCH v2 iproute2-next] ip link: add sub-command to view and change DSA master
Date: Thu, 22 Sep 2022 14:30:37 -0700 [thread overview]
Message-ID: <fa76bef5-50c5-d9d7-c2ed-e743dcbdcf2c@gmail.com> (raw)
In-Reply-To: <20220922212809.jameu6d4jtputjft@skbuf>
On 9/22/22 14:28, Vladimir Oltean wrote:
> On Thu, Sep 22, 2022 at 02:25:53PM -0700, Florian Fainelli wrote:
>> On 9/22/22 13:34, Andrew Lunn wrote:
>>>> Ok, if there aren't any objections, I will propose a v3 in 30 minutes or
>>>> so, with 'conduit' being the primary iproute2 keyword and 'master'
>>>> defined in the man page as a synonym for it, and the ip-link program
>>>> printing just 'conduit' in the help text but parsing both, and printing
>>>> just 'conduit' in the json output.
>>>
>>> Sounds good to me.
>>
>> Works for me as well! Thanks Vladimir.
>> --
>> Florian
>
> Hmm, did you see the parallel sub-thread with Jakub's proposed 'via'?
> I was kind of reworking to use that, and testing it right now. What do
> you prefer between the 2?
Emails crossed, I just responded to the parallel thread and do prefer
"conduit".
--
Florian
next prev parent reply other threads:[~2022-09-22 21:30 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-21 16:51 [PATCH v2 iproute2-next] ip link: add sub-command to view and change DSA master Vladimir Oltean
2022-09-21 18:36 ` Stephen Hemminger
2022-09-21 18:38 ` Vladimir Oltean
2022-09-21 22:33 ` Stephen Hemminger
2022-09-22 14:41 ` Vladimir Oltean
2022-09-22 15:30 ` Stephen Hemminger
2022-09-22 15:42 ` Andrew Lunn
2022-09-22 18:43 ` Vladimir Oltean
2022-09-22 19:04 ` Stephen Hemminger
2022-09-22 19:36 ` Vladimir Oltean
2022-09-22 20:34 ` Andrew Lunn
2022-09-22 21:25 ` Florian Fainelli
2022-09-22 21:28 ` Vladimir Oltean
2022-09-22 21:30 ` Florian Fainelli [this message]
2022-09-22 21:40 ` Vladimir Oltean
2022-09-22 21:41 ` Andrew Lunn
2022-09-22 21:52 ` Vladimir Oltean
2022-09-21 22:41 ` Stephen Hemminger
2022-09-22 1:30 ` Andrew Lunn
2022-09-22 13:24 ` Jakub Kicinski
2022-09-22 15:27 ` Stephen Hemminger
2022-09-22 15:36 ` Florian Fainelli
2022-09-22 18:00 ` Vladimir Oltean
2022-09-22 19:30 ` Jakub Kicinski
2022-09-22 20:13 ` Vladimir Oltean
2022-09-22 20:28 ` Stephen Hemminger
2022-09-22 20:36 ` Vladimir Oltean
2022-09-22 21:28 ` Florian Fainelli
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=fa76bef5-50c5-d9d7-c2ed-e743dcbdcf2c@gmail.com \
--to=f.fainelli@gmail.com \
--cc=andrew@lunn.ch \
--cc=dsahern@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.org \
--cc=vivien.didelot@gmail.com \
--cc=vladimir.oltean@nxp.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;
as well as URLs for NNTP newsgroup(s).