From: Jijie Shao <shaojijie@huawei.com>
To: Simon Horman <horms@kernel.org>
Cc: <shaojijie@huawei.com>, <davem@davemloft.net>,
<edumazet@google.com>, <kuba@kernel.org>, <pabeni@redhat.com>,
<andrew+netdev@lunn.ch>, <shenjian15@huawei.com>,
<liuyonglong@huawei.com>, <chenhao418@huawei.com>,
<huangdonghua3@h-partners.com>, <yangshuaisong@h-partners.com>,
<netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH V2 net-next 0/6] net: hns3: enhance tc flow offload support
Date: Wed, 27 May 2026 21:12:01 +0800 [thread overview]
Message-ID: <c6dc79ef-5f6e-4c97-97da-fa50eb1d1370@huawei.com> (raw)
In-Reply-To: <20260527095930.GI2256768@horms.kernel.org>
on 2026/5/27 17:59, Simon Horman wrote:
> On Sat, May 23, 2026 at 06:54:43PM +0800, Jijie Shao wrote:
>> This patchset enhances the tc flow offload support for hns3 driver:
>>
>> - Patch 1: Refactor hclge_add_cls_flower() to support more actions
>> - Patch 2: Improve unused_tuple parameter setting for separate src/dst configuration
>> - Patch 3: Add support for HCLGE_FD_ACTION_SELECT_QUEUE and HCLGE_FD_ACTION_DROP_PACKET actions
>> - Patch 4: Add support for FLOW_DISSECTOR_KEY_IP and FLOW_DISSECTOR_KEY_ENC_KEYID dissectors
>> - Patch 5: Add debugfs support for dumping FD rules
>> - Patch 6: Move FD code to a separate file (hclge_fd.c) for better code organization
>>
>> ---
>> ChangeLog:
>> v1 -> v2:
>> - Fixed warnings similar to "warning: restricted __le32 degrades to integer",
>> pointed out by Jakub
>> - Fixed warnings related to
>> "warning: diagnostic behavior may be improved by adding the 'format(printf, 5, 7)'",
>> pointed out by Jakub
>> v1: https://lore.kernel.org/all/20260518093526.1109595-1-shaojijie@huawei.com/
> Hi Juijie,
>
> There are AI-generated reviews of this patch-set available at
> https://netdev-ai.bots.linux.dev/ and https://sashiko.dev/
Hi,
I'm sorry, I don't understand how to use https://netdev-ai.bots.linux.dev/, it seems to require an API Token?
I find it difficult to locate my own patch-set in Recent Reviews.
Regarding https://sashiko.dev/, I checked and some of the issues are pre-existing issues,
not caused by the new features added in this patch-set.
Some others are related to the solution, which is the same as the ethtool -U already supported by the driver.
I suggest keeping it consistent with ethtool -U for now.
I will also check later whether modifications are needed. If the suggestion is reasonable,
I will send a separate patch to fix the code for both tc flow and ethtool -U.
For the remaining issues related to debugfs, I suggest they can be rejected.
Thanks,
Jijie Shao
next prev parent reply other threads:[~2026-05-27 13:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-23 10:54 Jijie Shao
2026-05-23 10:54 ` [PATCH V2 net-next 1/6] net: hns3: adjust add_cls_flower() for support more action Jijie Shao
2026-05-23 10:54 ` [PATCH V2 net-next 2/6] net: hns3: improve the unused_tuple parameter setting Jijie Shao
2026-05-23 10:54 ` [PATCH V2 net-next 3/6] net: hns3: support two more actions for tc flow Jijie Shao
2026-05-23 10:54 ` [PATCH V2 net-next 4/6] net: hns3: support IP and tunnel VNI dissectors " Jijie Shao
2026-05-23 10:54 ` [PATCH V2 net-next 5/6] net: hns3: debugfs support for dumping fd rules Jijie Shao
2026-05-23 10:54 ` [PATCH V2 net-next 6/6] net: hns3: move fd code to a separate file Jijie Shao
2026-05-27 9:59 ` [PATCH V2 net-next 0/6] net: hns3: enhance tc flow offload support Simon Horman
2026-05-27 13:12 ` Jijie Shao [this message]
2026-05-28 9:06 ` Paolo Abeni
2026-05-28 11:24 ` Jijie Shao
2026-05-29 9:34 ` Simon Horman
2026-06-02 12:23 ` Jijie Shao
2026-05-29 10:53 ` Paolo Abeni
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=c6dc79ef-5f6e-4c97-97da-fa50eb1d1370@huawei.com \
--to=shaojijie@huawei.com \
--cc=andrew+netdev@lunn.ch \
--cc=chenhao418@huawei.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=huangdonghua3@h-partners.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liuyonglong@huawei.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shenjian15@huawei.com \
--cc=yangshuaisong@h-partners.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
all inboxes | Powered by JetHome®