From: Eric Woudstra <ericwouds@gmail.com>
To: Heiner Kallweit <hkallweit1@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>, Andrew Lunn <andrew@lunn.ch>,
Russell King <linux@armlinux.org.uk>,
Matthias Brugger <matthias.bgg@gmail.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
Frank Wunderlich <frank-w@public-files.de>,
Daniel Golle <daniel@makrotopia.org>,
Lucien Jheng <lucien.jheng@airoha.com>,
Zhi-Jun You <hujy652@protonmail.com>
Cc: netdev@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH RFC net-next 2/2] Add the Airoha EN8811H PHY driver
Date: Sat, 16 Dec 2023 21:23:38 +0100 [thread overview]
Message-ID: <cd60b227-df1c-4fea-9554-695261c9d6a9@gmail.com> (raw)
In-Reply-To: <a0a47222-769b-4aaf-9143-1d7ad3e6ade9@gmail.com>
>
> Why don't you use the module_phy_driver() macro?
>
Thanks for the tip, I missed that in the conversion to recent kernel.
I will.
next prev parent reply other threads:[~2023-12-16 20:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-16 19:44 [PATCH RFC net-next 1/2] Add en8811h bindings documentation yaml Eric Woudstra
2023-12-16 19:44 ` [PATCH RFC net-next 2/2] Add the Airoha EN8811H PHY driver Eric Woudstra
2023-12-16 20:16 ` Heiner Kallweit
2023-12-16 20:23 ` Eric Woudstra [this message]
2023-12-16 23:33 ` Andrew Lunn
2023-12-18 8:44 ` [PATCH RFC net-next 1/2] Add en8811h bindings documentation yaml Krzysztof Kozlowski
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=cd60b227-df1c-4fea-9554-695261c9d6a9@gmail.com \
--to=ericwouds@gmail.com \
--cc=andrew@lunn.ch \
--cc=angelogioacchino.delregno@collabora.com \
--cc=conor+dt@kernel.org \
--cc=daniel@makrotopia.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=frank-w@public-files.de \
--cc=hkallweit1@gmail.com \
--cc=hujy652@protonmail.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=kuba@kernel.org \
--cc=linux@armlinux.org.uk \
--cc=lucien.jheng@airoha.com \
--cc=matthias.bgg@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).