Thread (24 messages) 24 messages, 12 authors, 2022-02-02

Re: [PATCH net-next] net: kbuild: Don't default net vendor configs to y

From: Saeed Mahameed <saeedm@nvidia.com>
Date: 2022-01-31 18:31:43
Also in: intel-wired-lan, linux-renesas-soc, linux-sunxi, lkml, netdev

On 31 Jan 09:59, Stephen Hemminger wrote:
On Mon, 31 Jan 2022 09:24:50 -0800
Saeed Mahameed [off-list ref] wrote:
quoted
From: Saeed Mahameed <saeedm@nvidia.com>

NET_VENDOR_XYZ were defaulted to 'y' for no technical reason.

Since all drivers belonging to a vendor are supposed to default to 'n',
defaulting all vendors to 'n' shouldn't be an issue, and aligns well
with the 'no new drivers' by default mentality.

Signed-off-by: Saeed Mahameed <saeedm@nvidia.com>
This was done back when vendors were introduced in the network drivers tree.
The default of Y allowed older configurations to just work.

So there was a reason, not sure if it matters anymore.
But it seems like useless repainting to change it now.
it sounds like it's useless to have it in first place, and it was and still
confusing to me why vendors need to by Y by default, can you explain what
are those "older configurations" ? 

The idea of this patch is to set a better example for new vendors and
to have a leaner  .config
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help