From: Damien Dejean <dam.dejean@gmail.com>
To: Paolo Abeni <pabeni@redhat.com>
Cc: andrew@lunn.ch, krzk+dt@kernel.org, robh@kernel.org,
kuba@kernel.org, maxime.chevallier@bootlin.com,
netdev@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, edumazet@google.com,
davem@davemloft.net, hkallweit1@gmail.com
Subject: Re: [PATCH v6 4/4] net: phy: realtek: add RTL8224 polarity support
Date: Sat, 21 Feb 2026 21:20:46 +0100 [thread overview]
Message-ID: <CB0A00EB-82D1-44AC-BBC8-8C676C89AD2E@gmail.com> (raw)
In-Reply-To: <def77227-7b69-4f23-8f68-949173eda6a4@redhat.com>
Hi Paolo,
> Le 11 févr. 2026 à 12:36, Paolo Abeni <pabeni@redhat.com> a écrit :
>
> This very close to what you implemented into patch 2/4. Likely you can
> deduplicate the code a bit factoring out some common helper.
Thanks for the feedback, let me rework this and repost once it is possible
Damien
>
> Side notes: you should include the target tree in the subj prefix -
> 'net-next' in this case, a per patch changelog for the introduced
> changes WRT the previous revision and a cover letter.
>
> Also note that net-next is now closed for the merge window; you will
> have to wait unit ~23 Feb before reposting.
>
> /P
>
>> }
>>
>> static int rtl8224_probe(struct phy_device *phydev)
>
next prev parent reply other threads:[~2026-02-21 20:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-07 9:25 [PATCH v6 1/4] dt-bindings: net: ethernet-phy: add property enet-phy-pair-order Damien Dejean
2026-02-07 9:25 ` [PATCH v6 2/4] net: phy: realtek: add RTL8224 pair order support Damien Dejean
2026-02-07 9:25 ` [PATCH v6 3/4] dt-bindings: net: ethernet-phy: add property enet-phy-pair-polarity Damien Dejean
2026-03-05 23:42 ` Rob Herring (Arm)
2026-02-07 9:25 ` [PATCH v6 4/4] net: phy: realtek: add RTL8224 polarity support Damien Dejean
2026-02-11 11:36 ` Paolo Abeni
2026-02-21 20:20 ` Damien Dejean [this message]
2026-03-05 23:41 ` [PATCH v6 1/4] dt-bindings: net: ethernet-phy: add property enet-phy-pair-order Rob Herring (Arm)
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=CB0A00EB-82D1-44AC-BBC8-8C676C89AD2E@gmail.com \
--to=dam.dejean@gmail.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maxime.chevallier@bootlin.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=robh@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