public inbox for linux-kbuild@vger.kernel.org
 help / color / mirror / Atom feed
From: Dragan Simic <dsimic@manjaro.org>
To: Jose Ignacio Tornos Martinez <jtornosm@redhat.com>
Cc: UNGLinuxDriver@microchip.com, andrew@lunn.ch,
	davem@davemloft.net, edumazet@google.com, f.fainelli@gmail.com,
	gregkh@linuxfoundation.org, 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, mcgrof@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 11:28:48 +0200	[thread overview]
Message-ID: <4db38805936d28fe1578c525a18f7849@manjaro.org> (raw)
In-Reply-To: <20240729083421.11203-1-jtornosm@redhat.com>

Hello Jose,

On 2024-07-29 10:34, Jose Ignacio Tornos Martinez wrote:
>> 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.
> 
> Well, I requested this commenting as an example the case of lan78xx and
> the possible phy modules,  becasue it is clearly failing when initramfs
> is generated due to the dynamic phy module loading process.
> In my opinion this example was enough good because I found it difficult 
> get
> an automatic way to get this information in advance for all the cases 
> and
> becasue I need to fix this initramfs issue.

I see and agree, but please note that other people highly disagree about
that being an issue at all.  Thus, I'd suggest that you provide a 
detailed
explanation of why and how that presents an issue that weakdeps solve.

> But with a first glance, I also found several examples (not phy 
> related),
> in which it seems the suitable softdep was added to solve the initramfs
> missing module issue:
> 80f4e62730a9 drm/panfrost: Mark simple_ondemand governor as softdep
> 0c94f58cef31 drm/lima: Mark simple_ondemand governor as softdep
> 2ebe16155dc8 scsi: ufs: core: Add soft dependency on 
> governor_simpleondemand
> dfe085d8dcd0 crypto: xts - Add softdep on ecb

Regarding Lima and Panfrost, I agree that weakdeps are a better solution
than softdeps, but please see also harddeps. [1]  I'd appreciate if 
you'd
provide your opinion about the proposed harddeps.

[1] 
https://lore.kernel.org/linux-modules/04e0676b0e77c5eb69df6972f41d77cdf061265a.1721906745.git.dsimic@manjaro.org/T/#u

> Therefore, I requested to provide this  kind of new dependency 
> (weakdep)
> first in general, becasue I thought it could be useful for a lot of 
> cases
> not only for the unkown (for initramfs) phy modules (i.e. lan78xx).
> That is, in spite of the initial usage has been rejected, I think it 
> can
> still be considered by the other commented examples (or new ones).
> I would like to confirm some example(s) to have some usage, but this 
> will
> need to be from September after my holidays.

Maybe we can have Lima and Panfrost as the first consumers, but I'd 
prefer
to have them use harddeps, as "earmarks" for the future (please see the
discussion linked above, and the two additional discussions linked from
the patch description in that thread).

  reply	other threads:[~2024-07-29  9:28 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
2024-07-29  8:34                                     ` Jose Ignacio Tornos Martinez
2024-07-29  9:28                                       ` Dragan Simic [this message]
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=4db38805936d28fe1578c525a18f7849@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