DPDK patches and discussions
 help / color / mirror / Atom feed
From: Dariusz Sosnowski <dsosnowski@nvidia.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: David Marchand <david.marchand@redhat.com>,
	Ali Alnubani <alialnu@nvidia.com>,
	Khadem Ullah <14pwcse1224@uetpeshawar.edu.pk>, <dev@dpdk.org>,
	Viacheslav Ovsiienko <viacheslavo@nvidia.com>,
	Bing Zhao <bingz@nvidia.com>, Ori Kam <orika@nvidia.com>,
	Suanming Mou <suanmingm@nvidia.com>,
	Matan Azrad <matan@nvidia.com>, <stable@dpdk.org>
Subject: Re: [PATCH v2] net/mlx5: fix connection tracking state item validation
Date: Wed, 20 Aug 2025 12:00:59 +0200	[thread overview]
Message-ID: <20250820100059.eatqpwvglkvzg3ad@ds-vm-debian.local> (raw)
In-Reply-To: <2610138.4XsnlVU6TS@thomas>

On Mon, Aug 18, 2025 at 07:20:19PM +0200, Thomas Monjalon wrote:
> 13/08/2025 16:16, Dariusz Sosnowski:
> > Hi,
> > 
> > Thank you for the patch. Please see comments inline.
> > 
> > On Tue, Aug 12, 2025 at 08:46:30AM -0400, Khadem Ullah wrote:
> > > This patch validate a connection tracking state when matching
> > > 'conntrack is' in rte_flow rules. Since conntrack item flags
> > > is a bitmap, then any combination of RTE_FLOW_CONNTRACK_PKT_STATE_*
> > > flags is a valid value to match on.
> > > 
> > > This patch validate the CT state item.
> > > Fixes: aca19061e4b9 ('net/mlx5: validate connection tracking item')
> > 
> > When used locally ./devtool/checkpatches.sh reports the following:
> > 
> > 	WARNING:BAD_FIXES_TAG: Please use correct Fixes: style 'Fixes: <12+ chars of sha1> ("<title line>")' - ie: 'Fixes: aca19061e4b9 ("net/mlx5: validate connection tracking item")'
> > 	#12:
> > 	Fixes: aca19061e4b9 ('net/mlx5: validate connection tracking item')
> > 
> > but it's not reported in "ci/checkpatch" job in Patchwork.
> > This check was added in Linux 6.1: https://github.com/torvalds/linux/commit/bd17e036b495bebbf07a5fc814c868e30e1dc131
> > so it appears that checkpatch.pl version used in CI is older than that.
> > Locally, I have a version from Linux 6.16.
> > 
> > Ali, Thomas, David: What do you think about updating the version of
> > checkpatch.pl used in community CI?
> 
> I've updated the checkpatch script used in the CI.
> It's the latest version from Linux minus few non-relevant checks.

Thank you Thomas

  reply	other threads:[~2025-08-20 10:02 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-05 13:23 [PATCH] " Khadem Ullah
2025-08-05 14:44 ` Ivan Malov
2025-08-06  8:51   ` Khadem Ullah
2025-08-08  7:47     ` Dariusz Sosnowski
2025-08-11  6:21       ` Khadem Ullah
2025-08-11 15:15         ` Dariusz Sosnowski
2025-08-11 16:27           ` Khadem Ullah
2025-08-11 17:18             ` Dariusz Sosnowski
2025-08-12  9:51               ` Dariusz Sosnowski
2025-08-12 12:50                 ` Khadem Ullah
2025-08-12 12:46 ` [PATCH v2] " Khadem Ullah
2025-08-13 14:16   ` Dariusz Sosnowski
2025-08-14  9:06     ` Khadem Ullah
2025-08-18 17:20     ` Thomas Monjalon
2025-08-20 10:00       ` Dariusz Sosnowski [this message]
2025-08-14  8:58   ` [PATCH v3] " Khadem Ullah
2025-08-14  9:33     ` Dariusz Sosnowski
2025-08-14 10:20       ` Khadem Ullah
2025-08-14 10:16     ` [PATCH v4] " Khadem Ullah
2025-08-14 11:43       ` Dariusz Sosnowski
2025-08-15 11:12     ` [PATCH] app/testpmd: add contrack state inspect commands commands Khadem Ullah
2025-08-15 11:15     ` [PATCH] app/testpmd: add contrack CT state inspect commands Khadem Ullah
2025-08-20 18:48       ` Stephen Hemminger
2025-08-12 12:41 [PATCH v2] net/mlx5: fix connection tracking state item validation Khadem Ullah

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=20250820100059.eatqpwvglkvzg3ad@ds-vm-debian.local \
    --to=dsosnowski@nvidia.com \
    --cc=14pwcse1224@uetpeshawar.edu.pk \
    --cc=alialnu@nvidia.com \
    --cc=bingz@nvidia.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=matan@nvidia.com \
    --cc=orika@nvidia.com \
    --cc=stable@dpdk.org \
    --cc=suanmingm@nvidia.com \
    --cc=thomas@monjalon.net \
    --cc=viacheslavo@nvidia.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;
as well as URLs for NNTP newsgroup(s).