From: patchwork-bot+netdevbpf@kernel.org
To: Qiao Ma <mqaio@linux.alibaba.com>
Cc: davem@davemloft.net, edumazet@google.com, pabeni@redhat.com,
kuba@kernel.org, gustavoars@kernel.org, cai.huoqing@linux.dev,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v4 0/2] net: hinic: fix bugs about dev_get_stats
Date: Wed, 06 Jul 2022 22:10:14 +0000 [thread overview]
Message-ID: <165714541459.11403.18049389885434650887.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1657019475.git.mqaio@linux.alibaba.com>
Hello:
This series was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:
On Tue, 5 Jul 2022 19:22:21 +0800 you wrote:
> These patches fixes 2 bugs of hinic driver:
> - fix bug that ethtool get wrong stats because of hinic_{txq|rxq}_clean_stats() is called
> - avoid kernel hung in hinic_get_stats64()
>
> See every patch for more information.
>
> Changes in v4:
> - removed meaningless u64_stats_sync protection in hinic_{txq|rxq}_get_stats
> - merged the third patch in v2 into first one
>
> [...]
Here is the summary with links:
- [net-next,v4,1/2] net: hinic: fix bug that ethtool get wrong stats
https://git.kernel.org/netdev/net-next/c/67dffd3db985
- [net-next,v4,2/2] net: hinic: avoid kernel hung in hinic_get_stats64()
https://git.kernel.org/netdev/net-next/c/98f9fcdee35a
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-07-06 22:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-05 11:22 [PATCH net-next v4 0/2] net: hinic: fix bugs about dev_get_stats Qiao Ma
2022-07-05 11:22 ` [PATCH net-next v4 1/2] net: hinic: fix bug that ethtool get wrong stats Qiao Ma
2022-07-05 11:22 ` [PATCH net-next v4 2/2] net: hinic: avoid kernel hung in hinic_get_stats64() Qiao Ma
2022-07-06 22: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=165714541459.11403.18049389885434650887.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=cai.huoqing@linux.dev \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gustavoars@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mqaio@linux.alibaba.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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.