public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Vladimir Oltean <vladimir.oltean@nxp.com>
Cc: netdev@vger.kernel.org, andrew@lunn.ch, hkallweit1@gmail.com,
	linux@armlinux.org.uk, davem@davemloft.net, edumazet@google.com,
	kuba@kernel.org, pabeni@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 net-next 0/4] Phylink link callback replay helpers for SJA1105 and XPCS
Date: Thu, 22 Jan 2026 04:00:29 +0000	[thread overview]
Message-ID: <176905442909.1550373.15597701384450224076.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260119121954.1624535-1-vladimir.oltean@nxp.com>

Hello:

This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Mon, 19 Jan 2026 14:19:50 +0200 you wrote:
> The sja1105 is reducing its direct interaction with the XPCS.
> 
> The changes presented here are an older simplification idea, broken out
> of a previous patch set to allow for more thorough review.
> 
> v2 submitted at:
> https://lore.kernel.org/netdev/20251118190530.580267-2-vladimir.oltean@nxp.com/
> v1 submitted at:
> https://lore.kernel.org/netdev/20241212172026.ivjkhm7s2qt6ejyz@skbuf/
> 
> [...]

Here is the summary with links:
  - [v3,net-next,1/4] net: phylink: simplify phylink_resolve() -> phylink_major_config() path
    https://git.kernel.org/netdev/net-next/c/7bf588dc62a0
  - [v3,net-next,2/4] net: phylink: introduce helpers for replaying link callbacks
    https://git.kernel.org/netdev/net-next/c/96969b132bf1
  - [v3,net-next,3/4] net: dsa: sja1105: let phylink help with the replay of link callbacks
    https://git.kernel.org/netdev/net-next/c/0b2edc531e0b
  - [v3,net-next,4/4] net: dsa: sja1105: re-merge sja1105_set_port_speed() and sja1105_set_port_config()
    https://git.kernel.org/netdev/net-next/c/ae73535c9d0f

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2026-01-22  4:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-19 12:19 [PATCH v3 net-next 0/4] Phylink link callback replay helpers for SJA1105 and XPCS Vladimir Oltean
2026-01-19 12:19 ` [PATCH v3 net-next 1/4] net: phylink: simplify phylink_resolve() -> phylink_major_config() path Vladimir Oltean
2026-01-19 13:57   ` Russell King (Oracle)
2026-01-19 12:19 ` [PATCH v3 net-next 2/4] net: phylink: introduce helpers for replaying link callbacks Vladimir Oltean
2026-01-19 14:03   ` Russell King (Oracle)
2026-01-19 12:19 ` [PATCH v3 net-next 3/4] net: dsa: sja1105: let phylink help with the replay of " Vladimir Oltean
2026-01-19 12:19 ` [PATCH v3 net-next 4/4] net: dsa: sja1105: re-merge sja1105_set_port_speed() and sja1105_set_port_config() Vladimir Oltean
2026-01-19 14:00 ` [PATCH v3 net-next 0/4] Phylink link callback replay helpers for SJA1105 and XPCS Russell King (Oracle)
2026-01-22  4:00 ` patchwork-bot+netdevbpf [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=176905442909.1550373.15597701384450224076.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=hkallweit1@gmail.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --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