From: Stephen Hemminger <stephen@networkplumber.org>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [PATCH net-next] net: kbuild: Don't default net vendor configs to y
Date: Mon, 31 Jan 2022 09:59:05 -0800 [thread overview]
Message-ID: <20220131095905.08722670@hermes.local> (raw)
In-Reply-To: <20220131172450.4905-1-saeed@kernel.org>
On Mon, 31 Jan 2022 09:24:50 -0800
Saeed Mahameed <saeed@kernel.org> wrote:
> 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.
next prev parent reply other threads:[~2022-01-31 17:59 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-31 17:24 [Intel-wired-lan] [PATCH net-next] net: kbuild: Don't default net vendor configs to y Saeed Mahameed
2022-01-31 17:59 ` Stephen Hemminger [this message]
2022-01-31 18:30 ` Geert Uytterhoeven
2022-01-31 18:35 ` Saeed Mahameed
2022-01-31 18:40 ` Florian Fainelli
2022-01-31 18:55 ` Hisashi T Fujinaka
2022-02-01 8:58 ` Leon Romanovsky
2022-02-01 15:46 ` Richard Cochran
2022-01-31 19:17 ` Richard Cochran
2022-01-31 20:10 ` Jakub Kicinski
2022-01-31 23:06 ` Florian Fainelli
2022-01-31 23:13 ` Jakub Kicinski
2022-01-31 23:19 ` Florian Fainelli
2022-02-02 4:46 ` Saeed Mahameed
2022-02-02 4:58 ` Jakub Kicinski
2022-02-02 5:16 ` Saeed Mahameed
2022-02-02 6:30 ` Christophe Leroy
2022-02-02 6:44 ` Saeed Mahameed
2022-02-02 6:49 ` Saeed Mahameed
2022-02-02 15:17 ` Richard Cochran
2022-02-02 15:31 ` Arnd Bergmann
2022-01-31 18:31 ` Saeed Mahameed
2022-01-31 18:04 ` Shannon Nelson
2022-01-31 19:13 ` Richard Cochran
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=20220131095905.08722670@hermes.local \
--to=stephen@networkplumber.org \
--cc=intel-wired-lan@osuosl.org \
/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