patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@amd.com>
To: Ori Kam <orika@nvidia.com>, Bing Zhao <bingz@nvidia.com>,
	"aman.deep.singh@intel.com" <aman.deep.singh@intel.com>,
	"yuying.zhang@intel.com" <yuying.zhang@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
	Alexander Kozyrev <akozyrev@nvidia.com>,
	"stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [PATCH] app/testpmd: fix the rule number parsing
Date: Mon, 10 Jul 2023 11:11:05 +0100	[thread overview]
Message-ID: <ab11cf30-d3ee-55a9-9ad3-b32eb9d830f3@amd.com> (raw)
In-Reply-To: <MW2PR12MB4666D6C9ACBE5097F69DB484D630A@MW2PR12MB4666.namprd12.prod.outlook.com>

On 7/10/2023 8:39 AM, Ori Kam wrote:
> Hi Bing
> 
>> -----Original Message-----
>> From: Bing Zhao <bingz@nvidia.com>
>> Sent: Friday, June 30, 2023 4:30 PM
>>
>> When creating a template table, the object pointer of the
>> command line "struct context" was set with an offset from the
>> original out buffer if there is a template ID.
>>
>> If the "rules_number" is specified after the template IDs, it
>> couldn't be set and passed to the API correctly. With this commit,
>> the pointer is reset before pasring the "rules_number" field.
>>
>> Fixes: c4b38873346b ("app/testpmd: add flow table management")
>> Cc: akozyrev@nvidia.com
>> Cc: stable@dpdk.org
>>
>> Signed-off-by: Bing Zhao <bingz@nvidia.com>
>> ---
> 
> Acked-by: Ori Kam <orika@nvidia.com>
> 

Applied to dpdk-next-net/main, thanks.

      reply	other threads:[~2023-07-10 10:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-30 13:30 Bing Zhao
2023-07-10  7:39 ` Ori Kam
2023-07-10 10:11   ` Ferruh Yigit [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=ab11cf30-d3ee-55a9-9ad3-b32eb9d830f3@amd.com \
    --to=ferruh.yigit@amd.com \
    --cc=akozyrev@nvidia.com \
    --cc=aman.deep.singh@intel.com \
    --cc=bingz@nvidia.com \
    --cc=dev@dpdk.org \
    --cc=orika@nvidia.com \
    --cc=stable@dpdk.org \
    --cc=yuying.zhang@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).