From: patchwork-bot+netdevbpf@kernel.org
To: David Thompson <davthompson@nvidia.com>
Cc: davem@davemloft.net, kuba@kernel.org, netdev@vger.kernel.org,
limings@nvidia.com, arnd@arndb.de, jgg@ziepe.ca,
=caihuoqing@baidu.com, asmaa@nvidia.com
Subject: Re: [PATCH net v2] mlxbf_gige: clear valid_polarity upon open
Date: Thu, 16 Sep 2021 13:40:07 +0000 [thread overview]
Message-ID: <163179960774.17264.3336487167553262857.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210915180848.32166-1-davthompson@nvidia.com>
Hello:
This patch was applied to netdev/net.git (refs/heads/master):
On Wed, 15 Sep 2021 14:08:48 -0400 you wrote:
> The network interface managed by the mlxbf_gige driver can
> get into a problem state where traffic does not flow.
> In this state, the interface will be up and enabled, but
> will stop processing received packets. This problem state
> will happen if three specific conditions occur:
> 1) driver has received more than (N * RxRingSize) packets but
> less than (N+1 * RxRingSize) packets, where N is an odd number
> Note: the command "ethtool -g <interface>" will display the
> current receive ring size, which currently defaults to 128
> 2) the driver's interface was disabled via "ifconfig oob_net0 down"
> during the window described in #1.
> 3) the driver's interface is re-enabled via "ifconfig oob_net0 up"
>
> [...]
Here is the summary with links:
- [net,v2] mlxbf_gige: clear valid_polarity upon open
https://git.kernel.org/netdev/net/c/ee8a9600b539
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:[~2021-09-16 13:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-15 18:08 [PATCH net v2] mlxbf_gige: clear valid_polarity upon open David Thompson
2021-09-16 13:40 ` 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=163179960774.17264.3336487167553262857.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc==caihuoqing@baidu.com \
--cc=arnd@arndb.de \
--cc=asmaa@nvidia.com \
--cc=davem@davemloft.net \
--cc=davthompson@nvidia.com \
--cc=jgg@ziepe.ca \
--cc=kuba@kernel.org \
--cc=limings@nvidia.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).