From: Dragan Simic <dsimic@manjaro.org>
To: Greg KH <gregkh@linuxfoundation.org>,
mcgrof@kernel.org, jtornosm@redhat.com
Cc: Andrew Lunn <andrew@lunn.ch>,
UNGLinuxDriver@microchip.com, davem@davemloft.net,
edumazet@google.com, f.fainelli@gmail.com, kuba@kernel.org,
linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-usb@vger.kernel.org, lucas.demarchi@intel.com,
masahiroy@kernel.org, netdev@vger.kernel.org, pabeni@redhat.com,
woojung.huh@microchip.com
Subject: Re: [PATCH] net: usb: lan78xx: add weak dependency with micrel phy module
Date: Mon, 29 Jul 2024 08:29:13 +0200 [thread overview]
Message-ID: <b8a2831c4f2d49469d5af04c03bb1a5b@manjaro.org> (raw)
In-Reply-To: <2024072923-galleria-gumdrop-5c56@gregkh>
Hello Greg, Jose and Luis,
On 2024-07-29 08:13, Greg KH wrote:
> On Mon, Jul 29, 2024 at 06:43:40AM +0200, Dragan Simic wrote:
>> On 2024-07-28 22:57, Andrew Lunn wrote:
>> > > In other words, this patch doesn't subtract anything. Instead, it
>> > > just
>> > > adds a weakdep link between the lan78xx and micrel modules, so the
>> > > kernel
>> > > itself can report that dependency, which may actually result in one
>> > > more
>> > > PHY driver added to a generated initial ramdisk.
>> >
>> > So at the moment, does the initramfs contain all PHY modules? I guess
>> > it does, because you have no knowledge which are actually needed. And
>> > this does not help you in any way, as you said, it does not subtract
>> > anything.
>>
>> Basically, an initial ramdisk shouldn't contain any PHY modules that
>> aren't automatically detected as needed on a particular system, for
>> which the initial ramdisk is built. That's how selecting modules
>> while building the initial ramdisks works. On the other hand, if it's
>> some initial ramdisk built by a Linux distribution and intended to
>> support multiple systems or boards, it may contain whatever the
>> distribution sees fit.
>>
>> Having weakdeps defined actually does help here. For example, a Linux
>> distribution mentioned above no longer needs to hand-craft the rules
>> for initial ramdisk generation for the PHY modules that should be put
>> into an initial ramdisk together with the lan78xx driver, if the Linux
>> distribution chooses to include the lax78xx driver. Having weakdep(s)
>> defined makes the kernel do that instead. Also, there's no point in
>> including every single PHY driver module, because not all of them are
>> needed for a particular selection of MAC drivers, which comes from the
>> intended purpose of the initial ramdisk built by a Linux distribution,
>> i.e. the target architecture, supported board category, etc.
>>
>> Let's also keep in mind that including all PHY modules into an initial
>> ramdisk inevitably makes it larger, which often isn't an option for
>> resource-constrained embedded systems.
>
> resource-constrained embedded systems know their dependancies and their
> hardware configurations, so I don't see how the weak-deps help at all
> here.
>
> You are arguing two different things it seems, neither of which this
> change helps out at all with, so I will provide a:
>
> Nacked-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
>
> here until it gets straightened out.
Quite frankly, all this makes me wonder why weakdeps were merged into
the mainline kernel [1] with no real consumers? Perhaps this is good
time for Jose and Luis to chime in.
[1]
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/include/linux/module.h?id=61842868de13aa7fd7391c626e889f4d6f1450bf
next prev parent reply other threads:[~2024-07-29 6:29 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240724145458.440023-1-jtornosm@redhat.com>
[not found] ` <20240724161020.442958-1-jtornosm@redhat.com>
[not found] ` <8a267e73-1acc-480f-a9b3-6c4517ba317a@lunn.ch>
[not found] ` <v6uovbn7ld3vlym65twtcvximgudddgvvhsh6heicbprcs5ii3@nernzyc5vu3i>
[not found] ` <32be761b-cebc-48e4-a36f-bbf90654df82@gmail.com>
2024-07-25 6:50 ` [PATCH] net: usb: lan78xx: add weak dependency with micrel phy module Lucas De Marchi
2024-07-25 9:53 ` Paolo Abeni
2024-07-26 11:33 ` Andrew Lunn
2024-07-26 12:15 ` Jose Ignacio Tornos Martinez
2024-07-26 20:59 ` Andrew Lunn
2024-07-27 17:15 ` Dragan Simic
2024-07-27 23:29 ` Andrew Lunn
2024-07-28 14:10 ` Dragan Simic
2024-07-28 19:45 ` Andrew Lunn
2024-07-28 20:46 ` Dragan Simic
2024-07-28 20:57 ` Andrew Lunn
2024-07-29 4:43 ` Dragan Simic
2024-07-29 6:13 ` Greg KH
2024-07-29 6:29 ` Dragan Simic [this message]
2024-07-29 8:34 ` Jose Ignacio Tornos Martinez
2024-07-29 9:28 ` Dragan Simic
2024-07-29 12:32 ` Jose Ignacio Tornos Martinez
2024-07-29 18:56 ` Andrew Lunn
2024-07-30 7:55 ` Jose Ignacio Tornos Martinez
2024-07-28 7:37 ` Masahiro Yamada
2024-07-28 9:53 ` Dragan Simic
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=b8a2831c4f2d49469d5af04c03bb1a5b@manjaro.org \
--to=dsimic@manjaro.org \
--cc=UNGLinuxDriver@microchip.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jtornosm@redhat.com \
--cc=kuba@kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=lucas.demarchi@intel.com \
--cc=masahiroy@kernel.org \
--cc=mcgrof@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=woojung.huh@microchip.com \
/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