From: Raslan Darawsheh <rasland@nvidia.com>
To: Erez Shitrit <erezsh@nvidia.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "stable@dpdk.org" <stable@dpdk.org>,
Matan Azrad <matan@nvidia.com>,
Slava Ovsiienko <viacheslavo@nvidia.com>
Subject: RE: [PATCH v4] net/mlx5/hws: fix bug in pattern creation
Date: Thu, 23 Mar 2023 07:19:28 +0000 [thread overview]
Message-ID: <BYAPR12MB30785C58F3F9A19F36F6C85CCF879@BYAPR12MB3078.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20230322144117.655848-1-erezsh@nvidia.com>
Hi,
> -----Original Message-----
> From: Erez Shitrit <erezsh@nvidia.com>
> Sent: Wednesday, March 22, 2023 4:41 PM
> To: dev@dpdk.org
> Cc: stable@dpdk.org; Matan Azrad <matan@nvidia.com>; Slava Ovsiienko
> <viacheslavo@nvidia.com>
> Subject: [PATCH v4] net/mlx5/hws: fix bug in pattern creation
>
>
> When creating a new pattern the data area should be clean, otherwise
> when the data will come from the arg object it will do OR operation on
> the data part in the pattern and use the dirty area as is.
>
> Now we clean the data area on each pattern creation.
>
> Fixes: f8c8a6d8440d ("net/mlx5/hws: add action object")
> Cc: stable@dpdk.org
>
> Signed-off-by: Erez Shitrit <erezsh@nvidia.com>
> Reviewed-by: Alex Vesker <valex@nvidia.com>
> Acked-by: Matan Azrad <matan@nvidia.com>
Patch applied to next-net-mlx,
Kindest regards,
Raslan Darawsheh
prev parent reply other threads:[~2023-03-23 7:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-22 10:16 [PATCH] " Erez Shitrit
2023-03-22 10:16 ` [PATCH] net/mlx5/hws: fix shared context to use local defaults Erez Shitrit
2023-03-22 12:26 ` Raslan Darawsheh
2023-03-22 14:42 ` [PATCH v4] " Erez Shitrit
2023-03-23 7:20 ` Raslan Darawsheh
2023-03-22 10:16 ` [PATCH] net/mlx5/hws: fix saving of jumbo tag for deletion Erez Shitrit
2023-03-22 14:44 ` [PATCH v4] " Erez Shitrit
2023-03-23 7:20 ` Raslan Darawsheh
2023-03-22 14:41 ` [PATCH v4] net/mlx5/hws: fix bug in pattern creation Erez Shitrit
2023-03-23 7:19 ` Raslan Darawsheh [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=BYAPR12MB30785C58F3F9A19F36F6C85CCF879@BYAPR12MB3078.namprd12.prod.outlook.com \
--to=rasland@nvidia.com \
--cc=dev@dpdk.org \
--cc=erezsh@nvidia.com \
--cc=matan@nvidia.com \
--cc=stable@dpdk.org \
--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).