From: patchwork-bot+netdevbpf@kernel.org
To: Fan Gong <gongfan1@huawei.com>
Cc: wudi234@huawei.com, tengpeisen@huawei.com,
netdev@vger.kernel.org, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, horms@kernel.org,
andrew+netdev@lunn.ch, ioana.ciornei@nxp.com,
maxime.chevallier@bootlin.com, mohsin.bashr@gmail.com,
dimitri.daskalakis1@gmail.com, hramamurthy@google.com,
larysa.zaremba@intel.com, vadim.fedorenko@linux.dev,
linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
zhoushuai28@huawei.com, wulike1@huawei.com
Subject: Re: [PATCH net-next v04 0/4] net: hinic3: Bugfix for later patch-set.
Date: Thu, 19 Nov 2026 02:20:05 +0000 [thread overview]
Message-ID: <179505480553.2718526.4549526677342724377.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1794917917.git.gongfan1@huawei.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 17 Nov 2026 20:08:30 +0800 you wrote:
> These issues were discovered by LLM Gemini-4-Argon and Claude-Opus-5-5.
> At the same time, LLM recommended submitting an independent patch.
> These issues were not actually triggered. Based on theoretical analysis
> and consideration of actual risks, this patch is used to fix the issues.
>
> Testing:
> This patch-set has been tested on hinic3 hardware.
>
> [...]
Here is the summary with links:
- [net-next,v04,1/4] hinic3: Fix the RX stalls in hinic3_rx_poll()
(no matching commit)
- [net-next,v04,2/4] hinic3: Read the queue counters once per u64_stats retry loop
https://git.kernel.org/netdev/net-next/c/0f00324913b4
- [net-next,v04,3/4] hinic3: Wrap long lines and rename q_params
https://git.kernel.org/netdev/net-next/c/b4cca5c5238e
- [net-next,v04,4/4] hinic3: Keep max_qps at the hardware maximum when RSS setup fails
https://git.kernel.org/netdev/net-next/c/453a026487a6
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:[~2026-11-19 2:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-17 12:08 [PATCH net-next v04 0/4] net: hinic3: Bugfix for later patch-set Fan Gong
2026-11-17 12:08 ` [PATCH net-next v04 1/4] hinic3: Fix the RX stalls in hinic3_rx_poll() Fan Gong
2026-11-19 2:09 ` Jakub Kicinski
2026-11-19 8:04 ` Fan Gong
2026-11-17 12:08 ` [PATCH net-next v04 2/4] hinic3: Read the queue counters once per u64_stats retry loop Fan Gong
2026-11-17 12:08 ` [PATCH net-next v04 3/4] hinic3: Wrap long lines and rename q_params Fan Gong
2026-11-17 12:08 ` [PATCH net-next v04 4/4] hinic3: Keep max_qps at the hardware maximum when RSS setup fails Fan Gong
2026-11-19 2:20 ` 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=179505480553.2718526.4549526677342724377.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=dimitri.daskalakis1@gmail.com \
--cc=edumazet@google.com \
--cc=gongfan1@huawei.com \
--cc=horms@kernel.org \
--cc=hramamurthy@google.com \
--cc=ioana.ciornei@nxp.com \
--cc=kuba@kernel.org \
--cc=larysa.zaremba@intel.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maxime.chevallier@bootlin.com \
--cc=mohsin.bashr@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=tengpeisen@huawei.com \
--cc=vadim.fedorenko@linux.dev \
--cc=wudi234@huawei.com \
--cc=wulike1@huawei.com \
--cc=zhoushuai28@huawei.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