From: Paolo Abeni <pabeni@redhat.com>
To: Nicolas Frayer <nfrayer@baylibre.com>,
nm@ti.com, ssantosh@kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, peter.ujfalusi@gmail.com,
vkoul@kernel.org, dmaengine@vger.kernel.org,
grygorii.strashko@ti.com, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, linux-omap@vger.kernel.org,
netdev@vger.kernel.org
Cc: khilman@baylibre.com, glaroque@baylibre.com
Subject: Re: [PATCH v4 4/4] net: ethernet: ti: davinci_mdio: Deferring probe when soc_device_match() returns NULL
Date: Thu, 10 Nov 2022 12:21:40 +0100 [thread overview]
Message-ID: <575fa0c61cb55845c4d3a646d0b1f48d782588a0.camel@redhat.com> (raw)
In-Reply-To: <20221108181144.433087-5-nfrayer@baylibre.com>
Hello,
On Tue, 2022-11-08 at 19:11 +0100, Nicolas Frayer wrote:
> When the k3 socinfo driver is built as a module, there is a possibility
> that it will probe after the davinci mdio driver. By deferring the mdio
> probe we allow the k3 socinfo to probe and register the
> soc_device_attribute structure needed by the mdio driver.
>
> Signed-off-by: Nicolas Frayer <nfrayer@baylibre.com>
I guess this one will go via the arm tree, right?
I'm dropping it from the netdev PW.
Thanks,
Paolo
next prev parent reply other threads:[~2022-11-10 11:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-08 18:11 [PATCH v4 0/4] soc: ti: Add module build support to the socinfo Nicolas Frayer
2022-11-08 18:11 ` [PATCH v4 1/4] soc: ti: Convert allocations to devm Nicolas Frayer
2022-11-08 18:11 ` [PATCH v4 2/4] soc: ti: Add module build support Nicolas Frayer
2022-11-08 18:18 ` Randy Dunlap
2022-11-24 9:04 ` Nicolas Frayer
2022-11-24 7:54 ` Péter Ujfalusi
2022-11-24 9:01 ` Nicolas Frayer
2022-11-08 18:11 ` [PATCH v4 3/4] dmaengine: ti: k3-udma: Deferring probe when soc_device_match() returns NULL Nicolas Frayer
2022-11-08 18:11 ` [PATCH v4 4/4] net: ethernet: ti: davinci_mdio: " Nicolas Frayer
2022-11-10 11:21 ` Paolo Abeni [this message]
2022-11-16 10:52 ` Nicolas Frayer
2022-11-23 15:59 ` Vignesh Raghavendra
2022-11-23 17:33 ` Kevin Hilman
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=575fa0c61cb55845c4d3a646d0b1f48d782588a0.camel@redhat.com \
--to=pabeni@redhat.com \
--cc=davem@davemloft.net \
--cc=dmaengine@vger.kernel.org \
--cc=edumazet@google.com \
--cc=glaroque@baylibre.com \
--cc=grygorii.strashko@ti.com \
--cc=khilman@baylibre.com \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nfrayer@baylibre.com \
--cc=nm@ti.com \
--cc=peter.ujfalusi@gmail.com \
--cc=ssantosh@kernel.org \
--cc=vkoul@kernel.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
all inboxes | Powered by JetHome®