mirror of https://lore.kernel.org/lkml/
 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, tee.min.tan@linux.intel.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next] net: phy: dp83867: implement configurability for SGMII in-band auto-negotiation
Date: Thu, 27 Nov 2025 03:16:45 +0000	[thread overview]
Message-ID: <176421340549.1916399.17100394278180351848.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251122110427.133035-1-vladimir.oltean@nxp.com>

Hello:

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

On Sat, 22 Nov 2025 13:04:27 +0200 you wrote:
> Implement the inband_caps() and config_inband() PHY driver methods, to
> allow working with PCS devices that do not support or want in-band to be
> used.
> 
> There is a complication due to existing logic from commit c76acfb7e19d
> ("net: phy: dp83867: retrigger SGMII AN when link change") which might
> re-enable what dp83867_config_inband() has disabled. So we need to
> modify dp83867_link_change_notify() to use phy_modify_changed() when
> temporarily disabling in-band autoneg. If the return code is 0, it means
> the original in-band was disabled and we need to keep it disabled.
> If the return code is 1, the original was enabled and we need to
> re-enable it. If negative, there was an error, which was silent before,
> and remains silent now.
> 
> [...]

Here is the summary with links:
  - [net-next] net: phy: dp83867: implement configurability for SGMII in-band auto-negotiation
    https://git.kernel.org/netdev/net-next/c/002373a8b01d

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



      reply	other threads:[~2025-11-27  3:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-22 11:04 Vladimir Oltean
2025-11-27  3:16 ` 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=176421340549.1916399.17100394278180351848.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=tee.min.tan@linux.intel.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

all inboxes | Powered by JetHome®