From: Florian Fainelli <f.fainelli@gmail.com>
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 15:19:58 -0800 [thread overview]
Message-ID: <dd1497ca-b1da-311a-e5fc-7c7265eb3ddf@gmail.com> (raw)
In-Reply-To: <20220131151315.4ec5f2d3@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>
On 1/31/2022 3:13 PM, Jakub Kicinski wrote:
> On Mon, 31 Jan 2022 15:06:01 -0800 Florian Fainelli wrote:
>>>> Right, but once you start hiding NET_VENDOR_DRIVER_XYZ under a
>>>> NET_VENDOR_XYZ Kconfig symbol dependency, if NET_VENDOR_XYZ is not set
>>>> to Y, then you have no way to select NET_VENDOR_DRIVER_XYZ and so your
>>>> old defconfig breaks.
>>>
>>> To be clear do we actually care about *old* configs or *def* configs?
>>
>> I think we care about oldconfig but maybe less so about defconfigs which
>> are in tree and can be updated.
>
> The oldconfigs would have to not be updated on any intervening kernel
> in the last 10+ years to break, right? Or is there another way that an
> oldconfig would not have the vendor config set to y at this point?
That sounds very unrealistic, so yes, I don't think at this point that
would happen. Even if you had your 15 year old .config file and ran make
oldconfig today, you would have some work to do to make sure it still
runs on your hardware.
--
Florian
next prev parent reply other threads:[~2022-01-31 23:19 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
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 [this message]
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=dd1497ca-b1da-311a-e5fc-7c7265eb3ddf@gmail.com \
--to=f.fainelli@gmail.com \
--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