Netdev List
 help / color / mirror / Atom feed
From: Vinod Koul <vkoul@kernel.org>
To: linux-phy@lists.infradead.org,
	 Vladimir Oltean <vladimir.oltean@nxp.com>
Cc: netdev@vger.kernel.org, Ioana Ciornei <ioana.ciornei@nxp.com>,
	 Neil Armstrong <neil.armstrong@linaro.org>,
	 Josua Mayer <josua@solid-run.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH phy-next 0/5] Lynx 28G SerDes: 25GbE support
Date: Thu, 14 May 2026 21:47:52 +0530	[thread overview]
Message-ID: <177877547268.1092446.15204675916496337123.b4-ty@kernel.org> (raw)
In-Reply-To: <20260511150023.1903577-1-vladimir.oltean@nxp.com>


On Mon, 11 May 2026 18:00:18 +0300, Vladimir Oltean wrote:
> This is the remainder of "Lynx 28G improvements part 2", previously
> submitted here:
> https://lore.kernel.org/linux-phy/176850672122.1082429.444623229961712368.robh@kernel.org/
> 
> but split up into smaller portions (merged separately):
> - https://lore.kernel.org/linux-phy/20260226182853.1103616-1-vladimir.oltean@nxp.com/
> - https://lore.kernel.org/linux-phy/20260321011451.1557091-1-vladimir.oltean@nxp.com/
> 
> [...]

Applied, thanks!

[1/5] dt-bindings: phy: lynx-28g: add compatible strings per SerDes and instantiation
      commit: 1561f12db08b1da1fe47ce9a5beff11adfd90ac8
[2/5] dt-bindings: phy: lynx-28g: add constraint on LX2162A lane indices
      commit: 37056ea140242681ccf706f63ad8c7366d89f5e3
[3/5] phy: lynx-28g: require an OF node to probe
      commit: c9d80e861034e2f3618065dc02b1de828aed24f6
[4/5] phy: lynx-28g: probe on per-SoC and per-instance compatible strings
      commit: 8c57247f5d9734d617862d320bd3894eec898298
[5/5] phy: lynx-28g: add support for 25GBASER
      commit: 1cab8fba5073962712fae3b763417af95ccf476a

Best regards,
-- 
~Vinod



      parent reply	other threads:[~2026-05-14 16:17 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-11 15:00 [PATCH phy-next 0/5] Lynx 28G SerDes: 25GbE support Vladimir Oltean
2026-05-11 15:00 ` [PATCH phy-next 1/5] dt-bindings: phy: lynx-28g: add compatible strings per SerDes and instantiation Vladimir Oltean
2026-05-11 15:00 ` [PATCH phy-next 2/5] dt-bindings: phy: lynx-28g: add constraint on LX2162A lane indices Vladimir Oltean
2026-05-11 16:30   ` Conor Dooley
2026-05-11 15:00 ` [PATCH phy-next 3/5] phy: lynx-28g: require an OF node to probe Vladimir Oltean
2026-05-12 15:01   ` Ioana Ciornei
2026-05-11 15:00 ` [PATCH phy-next 4/5] phy: lynx-28g: probe on per-SoC and per-instance compatible strings Vladimir Oltean
2026-05-12 15:02   ` Ioana Ciornei
2026-05-11 15:00 ` [PATCH phy-next 5/5] phy: lynx-28g: add support for 25GBASER Vladimir Oltean
2026-05-13 11:00   ` Josua Mayer
2026-05-13 11:22     ` Vladimir Oltean
2026-05-13 11:41       ` Josua Mayer
2026-05-14 14:32         ` Vladimir Oltean
2026-05-13 11:37   ` Josua Mayer
2026-05-13 11:44     ` Josua Mayer
2026-05-13 13:37     ` Vladimir Oltean
2026-05-13 14:50       ` Josua Mayer
2026-05-13 15:10         ` Vladimir Oltean
2026-05-14 14:39           ` Ioana Ciornei
2026-05-13 14:51 ` [PATCH phy-next 0/5] Lynx 28G SerDes: 25GbE support Josua Mayer
2026-05-14 16:17 ` Vinod Koul [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=177877547268.1092446.15204675916496337123.b4-ty@kernel.org \
    --to=vkoul@kernel.org \
    --cc=ioana.ciornei@nxp.com \
    --cc=josua@solid-run.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-phy@lists.infradead.org \
    --cc=neil.armstrong@linaro.org \
    --cc=netdev@vger.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