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.
WARNING: multiple messages have this Message-ID (diff)
From: Stephen Hemminger <stephen@networkplumber.org>
To: Saeed Mahameed <saeed@kernel.org>
Cc: "David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
Mark Einon <mark.einon@gmail.com>,
Lino Sanfilippo <LinoSanfilippo@gmx.de>,
Maxime Ripard <mripard@kernel.org>, Chen-Yu Tsai <wens@csie.org>,
Jernej Skrabec <jernej.skrabec@gmail.com>,
Shay Agroskin <shayagr@amazon.com>,
Arthur Kiyanovski <akiyano@amazon.com>,
David Arinzon <darinzon@amazon.com>,
Noam Dagan <ndagan@amazon.com>, Saeed Bishara <saeedb@amazon.com>,
Chris Snook <chris.snook@gmail.com>,
Nicolas Ferre <nicolas.ferre@microchip.com>,
Claudiu Beznea <claudiu.beznea@microchip.com>,
Hans Ulli Kroll <ulli.kroll@googlemail.com>,
Linus Walleij <linus.walleij@linaro.org>,
Jeroen de Borst <jeroendb@google.com>,
Catherine Sullivan <csully@google.com>,
David Awogbemila <awogbemila@google.com>,
Yisen Zhuang <yisen.zhuang@huawei.com>,
Salil Mehta <salil.mehta@huawei.com>,
Jesse Brandeburg <jesse.brandeburg@intel.com>,
Tony Nguyen <anthony.l.nguyen@intel.com>,
"K . Y . Srinivasan" <kys@microsoft.com>,
Haiyang Zhang <haiyangz@microsoft.com>,
Stephen Hemminger <sthemmin@microsoft.com>,
Wei Liu <wei.liu@kernel.org>, Dexuan Cui <decui@microsoft.com>,
Vladimir Oltean <vladimir.oltean@nxp.com>,
Claudiu Manoil <claudiu.manoil@nxp.com>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
UNGLinuxDriver@microchip.com, Jon Mason <jdmason@kudzu.us>,
Simon Horman <simon.horman@corigine.com>,
Rain River <rain.1986.08.12@gmail.com>,
Zhu Yanjun <zyjzyj2000@gmail.com>,
Shannon Nelson <snelson@pensando.io>,
drivers@pensando.io, Sergey Shtylyov <s.shtylyov@omp.ru>,
Jiri Pirko <jiri@resnulli.us>,
Edward Cree <ecree.xilinx@gmail.com>,
Martin Habets <habetsm.xilinx@gmail.com>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
Jose Abreu <Jose.Abreu@synopsys.com>,
Andy Gospodarek <andy@greyhouse.net>,
Michal Simek <michal.simek@xilinx.com>,
Saeed Mahameed <saeedm@nvidia.com>, Arnd Bergmann <arnd@arndb.de>,
Jacob Keller <jacob.e.keller@intel.com>,
Vegard Nossum <vegard.nossum@oracle.com>,
Rob Herring <robh@kernel.org>,
l.stelmach@samsung.com, rafal@milecki.pl,
Florian Fainelli <f.fainelli@gmail.com>,
Edwin Peer <edwin.peer@broadcom.com>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Michael Chan <michael.chan@broadcom.com>,
Richard Cochran <richardcochran@gmail.com>,
Gerhard Engleder <gerhard@engleder-embedded.com>,
Marcin Wojtas <mw@semihalf.com>,
Oleksij Rempel <linux@rempel-privat.de>,
Gabriel Somlo <gsomlo@gmail.com>, Joel Stanley <joel@jms.id.au>,
Slark Xiao <slark_xiao@163.com>,
Christophe Leroy <christophe.leroy@csgroup.eu>,
Liming Sun <limings@nvidia.com>,
David Thompson <davthompson@nvidia.com>,
Asmaa Mnebhi <asmaa@nvidia.com>,
Lars Povlsen <lars.povlsen@microchip.com>,
Horatiu Vultur <horatiu.vultur@microchip.com>,
Steen Hegelund <steen.hegelund@microchip.com>,
Prabhakar Kushwaha <pkushwaha@marvell.com>,
Omkar Kulkarni <okulkarni@marvell.com>,
Shai Malin <smalin@marvell.com>,
Randy Dunlap <rdunlap@infradead.org>,
Vignesh Raghavendra <vigneshr@ti.com>,
Stefan Wahren <stefan.wahren@i2se.com>,
Gary Guo <gary@garyguo.net>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-sunxi@lists.linux.dev, intel-wired-lan@lists.osuosl.org,
linux-hyperv@vger.kernel.org, oss-drivers@corigine.com,
linux-renesas-soc@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com
Subject: Re: [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: 48+ 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:24 ` Saeed Mahameed
2022-01-31 17:59 ` Stephen Hemminger [this message]
2022-01-31 17:59 ` Stephen Hemminger
2022-01-31 18:30 ` [Intel-wired-lan] " Geert Uytterhoeven
2022-01-31 18:30 ` Geert Uytterhoeven
2022-01-31 18:35 ` [Intel-wired-lan] " Saeed Mahameed
2022-01-31 18:35 ` Saeed Mahameed
2022-01-31 18:40 ` [Intel-wired-lan] " Florian Fainelli
2022-01-31 18:40 ` Florian Fainelli
2022-01-31 18:55 ` [Intel-wired-lan] " Hisashi T Fujinaka
2022-01-31 18:55 ` Hisashi T Fujinaka
2022-02-01 8:58 ` Leon Romanovsky
2022-02-01 8:58 ` Leon Romanovsky
2022-02-01 15:46 ` Richard Cochran
2022-02-01 15:46 ` Richard Cochran
2022-01-31 19:17 ` Richard Cochran
2022-01-31 19:17 ` Richard Cochran
2022-01-31 20:10 ` [Intel-wired-lan] " Jakub Kicinski
2022-01-31 20:10 ` Jakub Kicinski
2022-01-31 23:06 ` [Intel-wired-lan] " Florian Fainelli
2022-01-31 23:06 ` Florian Fainelli
2022-01-31 23:13 ` [Intel-wired-lan] " Jakub Kicinski
2022-01-31 23:13 ` Jakub Kicinski
2022-01-31 23:19 ` [Intel-wired-lan] " Florian Fainelli
2022-01-31 23:19 ` Florian Fainelli
2022-02-02 4:46 ` [Intel-wired-lan] " Saeed Mahameed
2022-02-02 4:46 ` Saeed Mahameed
2022-02-02 4:58 ` [Intel-wired-lan] " Jakub Kicinski
2022-02-02 4:58 ` Jakub Kicinski
2022-02-02 5:16 ` [Intel-wired-lan] " Saeed Mahameed
2022-02-02 5:16 ` Saeed Mahameed
2022-02-02 6:30 ` [Intel-wired-lan] " Christophe Leroy
2022-02-02 6:30 ` Christophe Leroy
2022-02-02 6:44 ` [Intel-wired-lan] " Saeed Mahameed
2022-02-02 6:44 ` Saeed Mahameed
2022-02-02 6:49 ` [Intel-wired-lan] " Saeed Mahameed
2022-02-02 6:49 ` Saeed Mahameed
2022-02-02 15:17 ` [Intel-wired-lan] " Richard Cochran
2022-02-02 15:17 ` Richard Cochran
2022-02-02 15:31 ` [Intel-wired-lan] " Arnd Bergmann
2022-02-02 15:31 ` Arnd Bergmann
2022-01-31 18:31 ` [Intel-wired-lan] " Saeed Mahameed
2022-01-31 18:31 ` Saeed Mahameed
2022-01-31 18:04 ` [Intel-wired-lan] " Shannon Nelson
2022-01-31 18:04 ` Shannon Nelson
2022-01-31 19:13 ` [Intel-wired-lan] " Richard Cochran
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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.