Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Subject: Re: [net-next PATCH v3] net: phy: Add 1000BASE-KX interface mode
From:   patchwork-bot+netdevbpf@kernel.org
Message-Id: <166238641457.11602.14140679950100520661.git-patchwork-notify@kernel.org>
Date:   Mon, 05 Sep 2022 14:00:14 +0000
References: <20220902220240.996257-1-sean.anderson@seco.com>
In-Reply-To: <20220902220240.996257-1-sean.anderson@seco.com>
To:     Sean Anderson <sean.anderson@seco.com>
Cc:     andrew@lunn.ch, hkallweit1@gmail.com, linux@armlinux.org.uk,
        netdev@vger.kernel.org, kuba@kernel.org, corbet@lwn.net,
        pabeni@redhat.com, olteanv@gmail.com, linux-doc@vger.kernel.org,
        linux-kernel@vger.kernel.org, edumazet@google.com,
        davem@davemloft.net, linux-phy@lists.infradead.org
Precedence: bulk

Hello:

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

On Fri,  2 Sep 2022 18:02:39 -0400 you wrote:
> Add 1000BASE-KX interface mode. This 1G backplane ethernet as described in
> clause 70. Clause 73 autonegotiation is mandatory, and only full duplex
> operation is supported.
> 
> Although at the PMA level this interface mode is identical to
> 1000BASE-X, it uses a different form of in-band autonegation. This
> justifies a separate interface mode, since the interface mode (along
> with the MLO_AN_* autonegotiation mode) sets the type of autonegotiation
> which will be used on a link. This results in more than just electrical
> differences between the link modes.
> 
> [...]

Here is the summary with links:
  - [net-next,v3] net: phy: Add 1000BASE-KX interface mode
    https://git.kernel.org/netdev/net-next/c/05ad5d4581c3

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