[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180902115851.2b224c23@redhat.com>
Date: Sun, 2 Sep 2018 11:58:51 +0200
From: Jiri Benc <jbenc@...hat.com>
To: Christian Brauner <christian.brauner@...onical.com>
Cc: David Miller <davem@...emloft.net>, nicolas.dichtel@...nd.com,
ktkhai@...tuozzo.com, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org, kuznet@....inr.ac.ru,
yoshfuji@...ux-ipv6.org, pombredanne@...b.com,
kstewart@...uxfoundation.org, gregkh@...uxfoundation.org,
dsahern@...il.com, fw@...len.de, lucien.xin@...il.com,
jakub.kicinski@...ronome.com
Subject: Re: [PATCH net-next 0/5] rtnetlink: add IFA_IF_NETNSID for
RTM_GETADDR
On Sat, 1 Sep 2018 20:47:05 +0200, Christian Brauner wrote:
> Sorry for the late reply. Yup, sounds good to me.
> But maybe IFA_TARGET_NETNSID to indicate that we're talking network
> namespaces here? Seems to me that NSID might give the wrong impression.
> I'll send v1 soon. I expect tomorrow or sometime next week.
On the other hand, we currently have IFLA_IF_NETNSID for the link
operations. IFA_IF_NETNSID is more consistent with the existing
attribute. It may be confusing to authors of user space programs to
have attribute names doing the same thing constructed differently for
different calls (IFLA_IF_NETNSID and IFA_TARGET_NETNSID).
As for the patch set itself, it makes sense to me, whatever the
final attribute name is.
Thanks,
Jiri
Powered by blists - more mailing lists