All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Russell King (Oracle) <rmk+kernel@armlinux.org.uk>
Cc: andrew@lunn.ch, hkallweit1@gmail.com, davem@davemloft.net,
	netdev@vger.kernel.org, kuba@kernel.org
Subject: Re: [PATCH net-next] net: phylink: Support disabling autonegotiation for PCS
Date: Tue, 19 Oct 2021 12:10:08 +0000	[thread overview]
Message-ID: <163464540839.1998.415977997251146521.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <E1mcmIc-005LpO-13@rmk-PC.armlinux.org.uk>

Hello:

This patch was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:

On Tue, 19 Oct 2021 11:24:50 +0100 you wrote:
> From: Robert Hancock <robert.hancock@calian.com>
> 
> The auto-negotiation state in the PCS as set by
> phylink_mii_c22_pcs_config was previously always enabled when the
> driver is configured for in-band autonegotiation, even if
> autonegotiation was disabled on the interface with ethtool. Update the
> code to set the BMCR_ANENABLE bit based on the interface's
> autonegotiation enabled state.
> 
> [...]

Here is the summary with links:
  - [net-next] net: phylink: Support disabling autonegotiation for PCS
    https://git.kernel.org/netdev/net-next/c/92817dad7dcb

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



  reply	other threads:[~2021-10-19 12:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-19 10:24 [PATCH net-next] net: phylink: Support disabling autonegotiation for PCS Russell King
2021-10-19 12:10 ` patchwork-bot+netdevbpf [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-06-30 17:49 Robert Hancock
2021-06-30 18:02 ` Russell King (Oracle)
2021-07-01 14:52 ` Russell King (Oracle)
2021-07-01 15:59   ` Russell King - ARM Linux admin

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=163464540839.1998.415977997251146521.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=hkallweit1@gmail.com \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=rmk+kernel@armlinux.org.uk \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.