All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Jijie Shao <shaojijie@huawei.com>
Cc: <davem@davemloft.net>, <edumazet@google.com>, <pabeni@redhat.com>,
	<andrew+netdev@lunn.ch>, <horms@kernel.org>,
	<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 net-next 5/6] net: hns3: debugfs support for dumping fd rules
Date: Tue, 19 May 2026 18:49:11 -0700	[thread overview]
Message-ID: <20260519184911.3b9e6ff7@kernel.org> (raw)
In-Reply-To: <20260518093526.1109595-6-shaojijie@huawei.com>

On Mon, 18 May 2026 17:35:25 +0800 Jijie Shao wrote:
> Currently, the tc tool only supports adding and deleting rules from
> the driver but does not support querying rules from the driver.
> 
> This patch adds a rule dump file in debugfs to check whether the driver's
> configuration matches the configuration issued by tc flow.

drivers/net/ethernet/hisilicon/hns3/hns3pf/hclge_debugfs.c:2155:25: warning: diagnostic behavior may be improved by adding the 'format(printf, 5, 7)' attribute to the declaration of 'hclge_fd_dump_ptr' [-Wmissing-format-attribute]
 2141 | static void hclge_fd_dump_ptr(struct seq_file *s,
      | __attribute__((format(printf, 5, 7))) 
 2142 |                               struct hclge_fd_rule *rule,
 2143 |                               u32 type, const char *name,
 2144 |                               const char *fmt,
 2145 |                               const void *key, const void *mask)
 2146 | {
 2147 |         if (rule->unused_tuple & BIT(type))
 2148 |                 return;
 2149 | 
 2150 |         seq_printf(s, "\t\t%s: ", name);
 2151 |         seq_printf(s, fmt, key);
 2152 |         seq_putc(s, '\n');
 2153 | 
 2154 |         seq_printf(s, "\t\t%s_mask: ", name);
 2155 |         seq_printf(s, fmt, mask);
      |                                ^

  reply	other threads:[~2026-05-20  1:49 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-18  9:35 [PATCH net-next 0/6] net: hns3: enhance tc flow offload support Jijie Shao
2026-05-18  9:35 ` [PATCH net-next 1/6] net: hns3: adjust add_cls_flower() for support more action Jijie Shao
2026-05-18  9:35 ` [PATCH net-next 2/6] net: hns3: improve the unused_tuple parameter setting Jijie Shao
2026-05-18  9:35 ` [PATCH net-next 3/6] net: hns3: support two more actions for tc flow Jijie Shao
2026-05-18  9:35 ` [PATCH net-next 4/6] net: hns3: support IP and tunnel VNI dissectors " Jijie Shao
2026-05-20  1:48   ` Jakub Kicinski
2026-05-21 10:38     ` Jijie Shao
2026-05-18  9:35 ` [PATCH net-next 5/6] net: hns3: debugfs support for dumping fd rules Jijie Shao
2026-05-20  1:49   ` Jakub Kicinski [this message]
2026-05-18  9:35 ` [PATCH net-next 6/6] net: hns3: move fd code to a separate file Jijie Shao

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=20260519184911.3b9e6ff7@kernel.org \
    --to=kuba@kernel.org \
    --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=linux-kernel@vger.kernel.org \
    --cc=liuyonglong@huawei.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=shaojijie@huawei.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 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.