From: Carlo Szelinsky <github@szelinsky.de>
To: kory.maincent@bootlin.com
Cc: andrew+netdev@lunn.ch, andrew@lunn.ch, corey@leavitt.info,
davem@davemloft.net, edumazet@google.com, github@szelinsky.de,
hkallweit1@gmail.com, kuba@kernel.org,
linux-kernel@vger.kernel.org, linux@armlinux.org.uk,
netdev@vger.kernel.org, o.rempel@pengutronix.de,
pabeni@redhat.com
Subject: Re: [PATCH RFC net-next 0/4] net: pse-pd: decouple controller lookup from MDIO probe
Date: Sun, 26 Apr 2026 23:25:08 +0200 [thread overview]
Message-ID: <20260426212508.110300-1-github@szelinsky.de> (raw)
In-Reply-To: <20260424144124.131837c7@kmaincent-XPS-13-7390>
Hey,
Thanks for all the help from multiple guys :-) I am currently busy with work, but I will take some time soon!
cheers Carlo
next prev parent reply other threads:[~2026-04-26 21:32 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-23 7:42 [PATCH RFC net-next 0/4] net: pse-pd: decouple controller lookup from MDIO probe Corey Leavitt
2026-04-23 7:42 ` Corey Leavitt via B4 Relay
2026-04-23 7:42 ` [PATCH RFC net-next 1/4] net: pse-pd: scope pse_control regulator handle to kref lifetime Corey Leavitt
2026-04-23 7:42 ` Corey Leavitt via B4 Relay
2026-04-24 8:36 ` Kory Maincent
2026-04-23 7:42 ` [PATCH RFC net-next 2/4] net: pse-pd: add notifier chain for controller lifecycle events Corey Leavitt
2026-04-23 7:42 ` Corey Leavitt via B4 Relay
2026-04-23 7:42 ` [PATCH RFC net-next 3/4] net: pse-pd: fire lifecycle events on controller register/unregister Corey Leavitt
2026-04-23 7:42 ` Corey Leavitt via B4 Relay
2026-04-23 7:42 ` [PATCH RFC net-next 4/4] net: phy: own phydev->psec via PSE notifier and remove fwnode_mdio hook Corey Leavitt
2026-04-23 7:42 ` Corey Leavitt via B4 Relay
2026-04-24 12:36 ` Kory Maincent
2026-05-28 19:15 ` Jonas Jelonek
2026-04-23 9:05 ` [PATCH RFC net-next 0/4] net: pse-pd: decouple controller lookup from MDIO probe Kory Maincent
2026-04-23 9:48 ` Corey Leavitt
2026-04-24 12:41 ` Kory Maincent
2026-04-26 21:25 ` Carlo Szelinsky [this message]
2026-05-02 20:10 ` Carlo Szelinsky
2026-05-05 4:36 ` Corey Leavitt
-- strict thread matches above, loose matches on Subject: below --
2026-04-25 6:33 Corey Leavitt
2026-04-23 7:22 Corey Leavitt
2026-04-23 8:40 ` Corey Leavitt
2026-04-23 12:08 ` Jonas Gorski
2026-04-24 1:28 ` Corey Leavitt
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=20260426212508.110300-1-github@szelinsky.de \
--to=github@szelinsky.de \
--cc=andrew+netdev@lunn.ch \
--cc=andrew@lunn.ch \
--cc=corey@leavitt.info \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=kory.maincent@bootlin.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=o.rempel@pengutronix.de \
--cc=pabeni@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.