From: patchwork-bot+netdevbpf@kernel.org
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
Subject: Re: [net-next PATCH v3] net: phy: Add 1000BASE-KX interface mode
Date: Mon, 05 Sep 2022 14:00:14 +0000 [thread overview]
Message-ID: <166238641457.11602.14140679950100520661.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220902220240.996257-1-sean.anderson@seco.com>
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
prev parent reply other threads:[~2022-09-05 14:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-02 22:02 [net-next PATCH v3] net: phy: Add 1000BASE-KX interface mode Sean Anderson
2022-09-05 14: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=166238641457.11602.14140679950100520661.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew@lunn.ch \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=pabeni@redhat.com \
--cc=sean.anderson@seco.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