From: Florian Fainelli <f.fainelli@gmail.com>
To: Jose Ignacio Tornos Martinez <jtornosm@redhat.com>,
andrew@lunn.ch, gregkh@linuxfoundation.org
Cc: UNGLinuxDriver@microchip.com, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org,
linux-kernel@vger.kernel.org, linux-usb@vger.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: Wed, 24 Jul 2024 08:31:30 -0700 [thread overview]
Message-ID: <999bc5f0-5b4c-4676-a085-ba2258c6a1d6@gmail.com> (raw)
In-Reply-To: <20240724144626.439632-1-jtornosm@redhat.com>
On 7/24/2024 7:46 AM, Jose Ignacio Tornos Martinez wrote:
> Hello Andrew,
>
>> Is MODULE_WEAKDEP new?
> Yes, and it has been merged into torvalds/linux.git from today:
> https://git.kernel.org/torvalds/c/f488790059fe7be6b2b059ddee10835b2500b603
> Here the commit reference in torvalds/linux.git if you update your repo:
> https://github.com/torvalds/linux/commit/61842868de13aa7fd7391c626e889f4d6f1450bf
What is the difference with the existing MODULE_SOFTDEP() which has pre
and post qualifiers and seems just as fit?
>
> I will include more references in case you want to get more information:
> kmod reference:
> https://github.com/kmod-project/kmod/commit/05828b4a6e9327a63ef94df544a042b5e9ce4fe7
> kmod test-suite has also been completed:
> https://github.com/kmod-project/kmod/commit/d06712b51404061eef92cb275b8303814fca86ec
> dracut patch has also been approved:
> https://github.com/dracut-ng/dracut-ng/commit/8517a6be5e20f4a6d87e55fce35ee3e29e2a1150
>
>> It seems like a "Wack a Mole" solution, which is not going to
>> scale. Does dracut not have a set of configuration files indicating
>> what modules should be included, using wildcards? If you want to have
>> NFS root, you need all the network drivers, and so you need all the
>> PHY drivers?
> The intention is to have a general solution not only related to the
> possible phy modules. That is, it is a solution for any module dependencies
> that are solved within the kernel but need to be known by user tools to
> build initramfs. We could use wildcards for some examples but it is not
> always easy to reference them.
> In addition, initramfs needs to be as small as possible so we should avoid
> wildcards and in this case, include the only possible phy modules (indeed
> not all phy's are compatible with a device). In this way, with the default
> behavior, initramfs would include only the drivers for the current machine
> and the only related phy modules.
>
> Thanks
>
> Best regards
> José Ignacio
>
>
--
Florian
next prev parent reply other threads:[~2024-07-24 15:31 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-24 10:23 Jose Ignacio Tornos Martinez
2024-07-24 11:49 ` Andrew Lunn
2024-07-24 13:36 ` Greg KH
2024-07-24 14:46 ` Jose Ignacio Tornos Martinez
2024-07-24 15:31 ` Florian Fainelli [this message]
2024-07-24 14:54 ` Jose Ignacio Tornos Martinez
2024-07-24 16:10 ` Jose Ignacio Tornos Martinez
2024-07-24 22:57 ` Andrew Lunn
2024-07-25 4:25 ` Lucas De Marchi
2024-07-25 4:42 ` Florian Fainelli
2024-07-25 6:50 ` 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
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
2024-07-26 14:49 ` Jakub Kicinski
2024-07-26 21:15 ` Andrew Lunn
2024-07-29 8:37 ` Jose Ignacio Tornos Martinez
2024-07-29 12:42 ` Andrew Lunn
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=999bc5f0-5b4c-4676-a085-ba2258c6a1d6@gmail.com \
--to=f.fainelli@gmail.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=jtornosm@redhat.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.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
all inboxes | Powered by JetHome®