From: patchwork-bot+netdevbpf@kernel.org
To: Erik Ekman <erik@kryo.se>
Cc: ecree.xilinx@gmail.com, habetsm.xilinx@gmail.com,
davem@davemloft.net, kuba@kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sfc: Fix reading non-legacy supported link modes
Date: Mon, 18 Oct 2021 13:30:10 +0000 [thread overview]
Message-ID: <163456381032.15402.834559957967695883.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20211017171657.85724-1-erik@kryo.se>
Hello:
This patch was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:
On Sun, 17 Oct 2021 19:16:57 +0200 you wrote:
> Everything except the first 32 bits was lost when the pause flags were
> added. This makes the 50000baseCR2 mode flag (bit 34) not appear.
>
> I have tested this with a 10G card (SFN5122F-R7) by modifying it to
> return a non-legacy link mode (10000baseCR).
>
> Signed-off-by: Erik Ekman <erik@kryo.se>
>
> [...]
Here is the summary with links:
- sfc: Fix reading non-legacy supported link modes
https://git.kernel.org/netdev/net-next/c/041c61488236
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2021-10-18 13:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-17 17:16 [PATCH] sfc: Fix reading non-legacy supported link modes Erik Ekman
2021-10-18 13:30 ` patchwork-bot+netdevbpf [this message]
2021-10-19 15:21 ` Andrew Lunn
2021-10-19 17:41 ` Erik Ekman
2021-10-19 18:29 ` Andrew Lunn
2021-10-25 18:58 ` Erik Ekman
2021-10-25 19:29 ` Erik Ekman
-- strict thread matches above, loose matches on Subject: below --
2021-11-03 11:12 Erik Ekman
2021-11-03 11:13 Erik Ekman
2021-11-03 11:15 Erik Ekman
2021-11-03 11:15 ` Erik Ekman
2021-11-04 8:18 ` Greg KH
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=163456381032.15402.834559957967695883.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=ecree.xilinx@gmail.com \
--cc=erik@kryo.se \
--cc=habetsm.xilinx@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/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.