From: Vladimir Oltean <olteanv@gmail.com>
To: Horatiu Vultur <horatiu.vultur@microchip.com>
Cc: Vladimir Oltean <vladimir.oltean@nxp.com>,
vkoul@kernel.org, kishon@kernel.org, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org,
linux-phy@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Daniel Golle <daniel@makrotopia.org>
Subject: Re: [PATCH 0/2] phy: microchip: lan966x: Allow to invert N and P signals
Date: Wed, 11 Feb 2026 14:22:54 +0200 [thread overview]
Message-ID: <20260211122254.4mwzmi5auxddsm5k@skbuf> (raw)
In-Reply-To: <20251119192326.4bflaqkh4zvz2rib@skbuf>
Hi Horatiu,
On Wed, Nov 19, 2025 at 09:23:26PM +0200, Vladimir Oltean wrote:
> > Anyway I can wait with this patch series until you get your changes in.
>
> I will keep you copied to the patch set which I hope to send later today.
The generic description I was talking about has been merged as commit
e7556b59ba65 ("phy: add phy_get_rx_polarity() and phy_get_tx_polarity()").
This set should be dropped from Patchwork. You can send a new version
after the merge window closes, or an RFC at any time.
--
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy
next prev parent reply other threads:[~2026-02-11 12:23 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-10 11:05 [PATCH 0/2] phy: microchip: lan966x: Allow to invert N and P signals Horatiu Vultur
2025-11-10 11:05 ` [PATCH 1/2] phy: microchip: lan966x: Add support for inverting the rx/tx lanes Horatiu Vultur
2025-11-10 11:05 ` [PATCH 2/2] dt-bindings: phy: lan966x: Add optional microchip,sx-tx/rx-inverted Horatiu Vultur
2025-11-10 18:43 ` Conor Dooley
2025-11-11 9:58 ` Horatiu Vultur
2025-11-11 10:06 ` Krzysztof Kozlowski
2025-11-11 17:39 ` Conor Dooley
2025-11-12 8:02 ` Horatiu Vultur
2025-11-12 18:32 ` Conor Dooley
2025-11-13 11:56 ` Horatiu Vultur
2025-11-13 19:13 ` Conor Dooley
2025-11-10 11:42 ` [PATCH 0/2] phy: microchip: lan966x: Allow to invert N and P signals Vladimir Oltean
2025-11-11 9:50 ` Horatiu Vultur
2025-11-13 16:30 ` Vladimir Oltean
2025-11-14 10:34 ` Horatiu Vultur
2025-11-19 19:23 ` Vladimir Oltean
2026-02-11 12:22 ` Vladimir Oltean [this message]
2026-02-12 8:02 ` Horatiu Vultur
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=20260211122254.4mwzmi5auxddsm5k@skbuf \
--to=olteanv@gmail.com \
--cc=conor+dt@kernel.org \
--cc=daniel@makrotopia.org \
--cc=devicetree@vger.kernel.org \
--cc=horatiu.vultur@microchip.com \
--cc=kishon@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=robh@kernel.org \
--cc=vkoul@kernel.org \
--cc=vladimir.oltean@nxp.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