From: Fan Gong <gongfan1@huawei.com>
To: <larysa.zaremba@intel.com>
Cc: <andrew+netdev@lunn.ch>, <august.hewei@huawei.com>,
<chenanwen@huawei.com>, <davem@davemloft.net>,
<dimitri.daskalakis1@gmail.com>, <edumazet@google.com>,
<gongfan1@huawei.com>, <guoxin09@huawei.com>, <horms@kernel.org>,
<hramamurthy@google.com>, <ioana.ciornei@nxp.com>,
<kuba@kernel.org>, <linux-doc@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <luosifu@huawei.com>,
<maxime.chevallier@bootlin.com>, <mohsin.bashr@gmail.com>,
<netdev@vger.kernel.org>, <pabeni@redhat.com>,
<shijing34@huawei.com>, <tengpeisen@huawei.com>,
<wudi234@huawei.com>, <wulike1@huawei.com>,
<zhengjiezhen@h-partners.com>, <zhoushuai28@huawei.com>
Subject: Re: Re: [PATCH net-next v12 1/8] hinic3: Fix drop skb when skb_checksum_help() fails
Date: Wed, 5 Aug 2026 10:15:36 +0800 [thread overview]
Message-ID: <20260805021537.1986-1-gongfan1@huawei.com> (raw)
In-Reply-To: <ams16FJUl0Oo-qC5@soc-5CG4396X81.clients.intel.com>
> Regarding patch 1/8 and 2/8 in this series. A change either fixes a bug or it
> does not. If it does, the patch must go the net tree and contain a Fixes: tag.
> If it is a prerequisite for your -next series, you need the fixes to be merged
> first (but it's usually not that long). If you are rather sure that the code
> inconsistency that you are correcting does not have any real negative impact
> (e.g. failure is only for features not supported by the netdev), it can go in a
> normal -next patch series, but it's best to explain, why it has no real
> functional impact and avoid using the word "fix", otherwise both humans and AIs
> can get confused.
Thanks for the feedback. You are right, these are actual fixes. We will split
them into a separate submission targeting the net tree, add the Fixes: tags,
and refine the commit logs based on your suggestions.
next prev parent reply other threads:[~2026-08-05 2:15 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-27 6:54 [PATCH net-next v12 0/8] net: hinic3: PF initialization Fan Gong
2026-07-27 6:54 ` [PATCH net-next v12 1/8] hinic3: Fix drop skb when skb_checksum_help() fails Fan Gong
2026-07-30 11:30 ` Larysa Zaremba
2026-08-05 2:15 ` Fan Gong [this message]
2026-08-03 23:07 ` Jakub Kicinski
2026-08-05 2:30 ` Re: [PATCH net-next v12 1/8] hinic3: Fix drop skb when Fan Gong
2026-07-27 6:54 ` [PATCH net-next v12 2/8] hinic3: Fix loose success check in rx buffer filling Fan Gong
2026-07-27 16:37 ` Mohsin Bashir
2026-07-29 7:44 ` Fan Gong
2026-08-03 23:13 ` Jakub Kicinski
2026-08-05 2:22 ` Fan Gong
2026-07-27 6:54 ` [PATCH net-next v12 3/8] hinic3: Refactor channel state machine for dynamic queue configuration Fan Gong
2026-07-27 6:54 ` [PATCH net-next v12 4/8] hinic3: Add ethtool queue ops Fan Gong
2026-07-27 6:54 ` [PATCH net-next v12 5/8] hinic3: Add ethtool statistic ops Fan Gong
2026-07-27 6:54 ` [PATCH net-next v12 6/8] hinic3: Add ethtool coalesce ops Fan Gong
2026-07-27 6:54 ` [PATCH net-next v12 7/8] hinic3: Add ethtool rss ops Fan Gong
2026-07-27 6:54 ` [PATCH net-next v12 8/8] hinic3: Remove unneeded coalesce parameters Fan Gong
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=20260805021537.1986-1-gongfan1@huawei.com \
--to=gongfan1@huawei.com \
--cc=andrew+netdev@lunn.ch \
--cc=august.hewei@huawei.com \
--cc=chenanwen@huawei.com \
--cc=davem@davemloft.net \
--cc=dimitri.daskalakis1@gmail.com \
--cc=edumazet@google.com \
--cc=guoxin09@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=luosifu@huawei.com \
--cc=maxime.chevallier@bootlin.com \
--cc=mohsin.bashr@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shijing34@huawei.com \
--cc=tengpeisen@huawei.com \
--cc=wudi234@huawei.com \
--cc=wulike1@huawei.com \
--cc=zhengjiezhen@h-partners.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