DPDK patches and discussions
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: Soumyadeep Hore <soumyadeep.hore@intel.com>
Cc: <aman.deep.singh@intel.com>, <dev@dpdk.org>
Subject: Re: [PATCH v4 0/2] Avoid rule duplication in CPFL PMD
Date: Fri, 5 Jul 2024 15:47:25 +0100	[thread overview]
Message-ID: <ZogHffK2w9PTomII@bricha3-mobl1.ger.corp.intel.com> (raw)
In-Reply-To: <20240705130515.3090598-1-soumyadeep.hore@intel.com>

On Fri, Jul 05, 2024 at 01:05:13PM +0000, Soumyadeep Hore wrote:
> This patchset avoids flow rule duplication which was possible
> previously in CPFL PMD.
> 
> ---
> v4:
> * Addressed pending review comments
> ---
> v3:
> * Addressed pending review comments
> ---
> v2:
> * Addressed review comments
> * Added Fixes tags
> * Fixed CI warnings
> ---
> 
> Soumyadeep Hore (2):
>   net/cpfl: fix check for opcodes of received ctlq messages
>   net/cpfl: fix +ve error codes for received ctlq messages
> 

Following discussion with the author, I've applied these two patches and
squashed them back into a single commit since both are needed together,
with the patch 2 being required because of the patch 1 changes - something
I missed on initial review.

Patches Acked-by: Bruce Richardson <bruce.richardson@intel.com>

Applied to dpdk-next-net-intel, with suggested minor changes.

Thanks,
/Bruce

      parent reply	other threads:[~2024-07-05 14:47 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-04  5:18 [PATCH v1] net/cpfl: add checks for received ctlq messages Soumyadeep Hore
2024-07-04 12:49 ` Bruce Richardson
2024-07-05  5:08 ` [PATCH v2 0/2] Avoid rule duplication in CPFL PMD Soumyadeep Hore
2024-07-05  5:08   ` [PATCH v2 1/2] net/cpfl: fix check for opcodes of received ctlq messages Soumyadeep Hore
2024-07-05  5:08   ` [PATCH v2 2/2] net/cpfl: fix +ve error codes for " Soumyadeep Hore
2024-07-05  8:30     ` [PATCH v3 0/2] Avoid rule duplication in CPFL PMD Soumyadeep Hore
2024-07-05  8:30       ` [PATCH v3 1/2] net/cpfl: fix check for opcodes of received ctlq messages Soumyadeep Hore
2024-07-05  9:49         ` Bruce Richardson
2024-07-05  8:30       ` [PATCH v3 2/2] net/cpfl: fix +ve error codes for " Soumyadeep Hore
2024-07-05 13:05         ` [PATCH v4 0/2] Avoid rule duplication in CPFL PMD Soumyadeep Hore
2024-07-05 13:05           ` [PATCH v4 1/2] net/cpfl: fix check for opcodes of received ctlq messages Soumyadeep Hore
2024-07-05 14:21             ` Bruce Richardson
2024-07-05 13:05           ` [PATCH v4 2/2] net/cpfl: fix +ve error codes for " Soumyadeep Hore
2024-07-05 14:47           ` Bruce Richardson [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=ZogHffK2w9PTomII@bricha3-mobl1.ger.corp.intel.com \
    --to=bruce.richardson@intel.com \
    --cc=aman.deep.singh@intel.com \
    --cc=dev@dpdk.org \
    --cc=soumyadeep.hore@intel.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).