From: Raslan Darawsheh <rasland@nvidia.com>
To: Asaf Penso <asafp@nvidia.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: NBU-Contact-Thomas Monjalon <thomas@monjalon.net>,
Slava Ovsiienko <viacheslavo@nvidia.com>,
Matan Azrad <matan@nvidia.com>,
"stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-stable] [PATCH 1/1] net/mlx5: fix typo in flow engine type
Date: Thu, 29 Jul 2021 08:20:00 +0000 [thread overview]
Message-ID: <DM4PR12MB5054DA4ACB333C9E22BD48A4CFEB9@DM4PR12MB5054.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20210728093946.752300-1-asafp@nvidia.com>
Hi,
> -----Original Message-----
> From: Asaf Penso <asafp@nvidia.com>
> Sent: Wednesday, July 28, 2021 12:40 PM
> To: dev@dpdk.org
> Cc: NBU-Contact-Thomas Monjalon <thomas@monjalon.net>; Slava
> Ovsiienko <viacheslavo@nvidia.com>; Matan Azrad <matan@nvidia.com>;
> Raslan Darawsheh <rasland@nvidia.com>; stable@dpdk.org
> Subject: [PATCH 1/1] net/mlx5: fix typo in flow engine type
>
> The concrete function names have a prefix for flow_dv.
> This emphasizes the flow engine is direct verbs.
>
> The function flow_get_aged_flows doesn’t have this prefix.
> It creates an inconsistency with the other functions.
>
> Update the function name to include dv.
>
> Fixes: fa2d01c87d2 ("net/mlx5: support flow aging")
> Cc: stable@dpdk.org
>
> Signed-off-by: Asaf Penso <asafp@nvidia.com>
> ---
Patch applied to next-net-mlx,
Kindest regards,
Raslan Darawsheh
prev parent reply other threads:[~2021-07-29 8:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-28 9:39 Asaf Penso
2021-07-28 9:55 ` Matan Azrad
2021-07-29 8:20 ` 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=DM4PR12MB5054DA4ACB333C9E22BD48A4CFEB9@DM4PR12MB5054.namprd12.prod.outlook.com \
--to=rasland@nvidia.com \
--cc=asafp@nvidia.com \
--cc=dev@dpdk.org \
--cc=matan@nvidia.com \
--cc=stable@dpdk.org \
--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).