[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220811124244.37a66b98@kernel.org>
Date: Thu, 11 Aug 2022 12:42:44 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: sdf@...gle.com
Cc: Stephen Hemminger <stephen@...workplumber.org>,
netdev@...r.kernel.org, davem@...emloft.net, edumazet@...gle.com,
pabeni@...hat.com, jacob.e.keller@...el.com, vadfed@...com,
johannes@...solutions.net, jiri@...nulli.us, dsahern@...nel.org,
fw@...len.de, linux-doc@...r.kernel.org,
Michal Kubecek <mkubecek@...e.cz>
Subject: Re: [RFC net-next 0/4] ynl: YAML netlink protocol descriptions
On Thu, 11 Aug 2022 09:28:45 -0700 sdf@...gle.com wrote:
> Putting it into iproute2 will make it carry a 'networking' badge on it
> meaning no other subsystem would look into it.
Good point.
> I'd rather make netlink more generic (s/netlink/kernelink/?) and remove
> CONFIG_NET dependency to address https://lwn.net/Articles/897202/
I think people just use that as an excuse, TBH.
Powered by blists - more mailing lists