From: Vladimir Oltean <vladimir.oltean@nxp.com>
To: linux-phy@lists.infradead.org, Vinod Koul <vkoul@kernel.org>,
Neil Armstrong <neil.armstrong@linaro.org>
Cc: netdev@vger.kernel.org, Ioana Ciornei <ioana.ciornei@nxp.com>,
Kishon Vijay Abraham I <kishon@kernel.org>,
Josua Mayer <josua@solid-run.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH phy 0/8] Lynx 28G improvements part 2
Date: Mon, 2 Feb 2026 17:03:08 +0200 [thread overview]
Message-ID: <20260202150308.d45z53mhvent664h@skbuf> (raw)
In-Reply-To: <20260114152111.625350-1-vladimir.oltean@nxp.com>
Hello PHY maintainers,
On Wed, Jan 14, 2026 at 05:21:03PM +0200, Vladimir Oltean wrote:
> This contains a number of changes deferred from part 1 (patches 1-6):
> https://lore.kernel.org/linux-phy/20251125114847.804961-1-vladimir.oltean@nxp.com/
>
> They are reworked in ways detailed in their individual change logs.
>
> I have a special request to linux-phy maintainers: after merging, please
> provide a stable branch/tag of this plus part 1, that can be pulled into
> netdev. It is needed because phy_exit() calls from consumers would
> compile but would cause a functionally broken link, so we need a linear
> git history to avoid (temporary) regressions.
Given how close to the merge window we are, I am dropping my special
request for a stable tag. But can you please take a look at this until
the merge window opens? It will simplify further development to have it
for v6.20 (or whatever next release number will be).
prev parent reply other threads:[~2026-02-02 15:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-14 15:21 [PATCH phy 0/8] Lynx 28G improvements part 2 Vladimir Oltean
2026-01-14 15:21 ` [PATCH phy 1/8] phy: lynx-28g: skip CDR lock workaround for lanes disabled in the device tree Vladimir Oltean
2026-01-14 15:21 ` [PATCH phy 2/8] dt-bindings: phy: lynx-28g: add compatible strings per SerDes and instantiation Vladimir Oltean
2026-01-15 19:52 ` Rob Herring (Arm)
2026-01-14 15:21 ` [PATCH phy 3/8] dt-bindings: phy: lynx-28g: add constraint on LX2162A lane indices Vladimir Oltean
2026-01-14 15:21 ` [PATCH phy 4/8] phy: lynx-28g: probe on per-SoC and per-instance compatible strings Vladimir Oltean
2026-01-14 15:21 ` [PATCH phy 5/8] phy: lynx-28g: add support for 25GBASER Vladimir Oltean
2026-01-14 15:21 ` [PATCH phy 6/8] phy: lynx-28g: use timeouts when waiting for lane halt and reset Vladimir Oltean
2026-01-14 15:21 ` [PATCH phy 7/8] phy: lynx-28g: truly power the lanes up or down Vladimir Oltean
2026-01-14 15:21 ` [PATCH phy 8/8] phy: lynx-28g: implement phy_exit() operation Vladimir Oltean
2026-02-02 15:03 ` Vladimir Oltean [this message]
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=20260202150308.d45z53mhvent664h@skbuf \
--to=vladimir.oltean@nxp.com \
--cc=ioana.ciornei@nxp.com \
--cc=josua@solid-run.com \
--cc=kishon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=neil.armstrong@linaro.org \
--cc=netdev@vger.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