All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Tom Lendacky <thomas.lendacky@amd.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
	pabeni@redhat.com, Shyam-sundar.S-k@amd.com
Subject: Re: [PATCH net 0/2] AMD XGBE active/passive cable fixes
Date: Mon, 12 Dec 2022 10:10:16 +0000	[thread overview]
Message-ID: <167083981663.16910.3529522370154591077.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1670516545.git.thomas.lendacky@amd.com>

Hello:

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

On Thu, 8 Dec 2022 10:22:23 -0600 you wrote:
> This series fixes some issues related to active and passive cables and
> consists of two patches:
> 
> - Provide proper recognition of active cables.
> 
> - Only check for a minimum supported speed for passive cables.
> 
> [...]

Here is the summary with links:
  - [net,1/2] net: amd-xgbe: Fix logic around active and passive cables
    https://git.kernel.org/netdev/net/c/4998006c73af
  - [net,2/2] net: amd-xgbe: Check only the minimum speed for active/passive cables
    https://git.kernel.org/netdev/net/c/f8ab263d4d48

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



      parent reply	other threads:[~2022-12-12 10:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-08 16:22 [PATCH net 0/2] AMD XGBE active/passive cable fixes Tom Lendacky
2022-12-08 16:22 ` [PATCH net 1/2] net: amd-xgbe: Fix logic around active and passive cables Tom Lendacky
2022-12-08 16:22 ` [PATCH net 2/2] net: amd-xgbe: Check only the minimum speed for active/passive cables Tom Lendacky
2022-12-12 10:10 ` 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=167083981663.16910.3529522370154591077.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=Shyam-sundar.S-k@amd.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=thomas.lendacky@amd.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 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.