[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <848592e3-4824-8369-c75f-5ade994973bd@gmail.com>
Date: Sat, 13 Feb 2021 17:16:19 -0800
From: Florian Fainelli <f.fainelli@...il.com>
To: Vladimir Oltean <olteanv@...il.com>,
"David S . Miller" <davem@...emloft.net>,
Jakub Kicinski <kuba@...nel.org>, netdev@...r.kernel.org
Cc: Andrew Lunn <andrew@...n.ch>,
Vivien Didelot <vivien.didelot@...il.com>,
Kurt Kanzenbach <kurt@...utronix.de>,
Woojung Huh <woojung.huh@...rochip.com>,
Linus Walleij <linus.walleij@...aro.org>,
Hauke Mehrtens <hauke@...ke-m.de>,
Jiri Pirko <jiri@...nulli.us>,
Ivan Vecera <ivecera@...hat.com>,
Roopa Prabhu <roopa@...dia.com>,
Nikolay Aleksandrov <nikolay@...dia.com>,
DENG Qingfang <dqfext@...il.com>,
Ido Schimmel <idosch@...sch.org>
Subject: Re: [PATCH net-next 4/5] net: dsa: propagate extack to .port_vlan_add
On 2/13/2021 12:43, Vladimir Oltean wrote:
> From: Vladimir Oltean <vladimir.oltean@....com>
>
> Allow drivers to communicate their restrictions to user space directly,
> instead of printing to the kernel log. Where the conversion would have
> been lossy and things like VLAN ID could no longer be conveyed (due to
> the lack of support for printf format specifier in netlink extack), I
> chose to keep the messages in full form to the kernel log only, and
> leave it up to individual driver maintainers to move more messages to
> extack.
>
> Signed-off-by: Vladimir Oltean <vladimir.oltean@....com>
Reviewed-by: Florian Fainelli <f.fainelli@...il.com>
--
Florian
Powered by blists - more mailing lists