From: Jakub Kicinski <kuba@kernel.org>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Jose Ignacio Tornos Martinez <jtornosm@redhat.com>,
UNGLinuxDriver@microchip.com, davem@davemloft.net,
edumazet@google.com, gregkh@linuxfoundation.org,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
lucas.demarchi@intel.com, 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: Fri, 26 Jul 2024 07:49:25 -0700 [thread overview]
Message-ID: <20240726074925.1c7df571@kernel.org> (raw)
In-Reply-To: <8a267e73-1acc-480f-a9b3-6c4517ba317a@lunn.ch>
On Thu, 25 Jul 2024 00:57:05 +0200 Andrew Lunn wrote:
> Maybe a better solution is to first build an initramfs with
> everything, plus the kitchen sink. Boot it, and then look at what has
> been loaded in order to get the rootfs mounted. Then update the
> initramfs with just what is needed? That should be pretty generic,
> with throw out networking ig NFS root is not used, just load JFFS2 and
> a NAND driver if it was used for the rootfs, etc.
Sorry for a dumb question from the audience but how does this work
for PCI devices? We don't worry about what drivers may be needed
because there's no "fallback / generic" driver?
For MDIO are the ID registers too complicated to expose to user space
and let it match the drivers using modinfo (avoiding the need to boot
a kitchen sink kernel)?
next prev parent reply other threads:[~2024-07-26 14:49 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-24 10:23 [PATCH] net: usb: lan78xx: add weak dependency with micrel phy module 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
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 [this message]
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=20240726074925.1c7df571@kernel.org \
--to=kuba@kernel.org \
--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=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=lucas.demarchi@intel.com \
--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;
as well as URLs for NNTP newsgroup(s).