From: Ori Kam <orika@nvidia.com>
To: Slava Ovsiienko <viacheslavo@nvidia.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: Raslan Darawsheh <rasland@nvidia.com>,
Matan Azrad <matan@nvidia.com>,
Shahaf Shuler <shahafs@nvidia.com>,
Gregory Etelson <getelson@nvidia.com>,
NBU-Contact-Thomas Monjalon <thomas@monjalon.net>,
"stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-stable] [PATCH v3 2/5] ethdev: fix missed experimental tag for modify field action
Date: Tue, 12 Oct 2021 08:13:54 +0000 [thread overview]
Message-ID: <DM8PR12MB5400E4CE95A59DBD11AC5F5CD6B69@DM8PR12MB5400.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20211012080631.28504-3-viacheslavo@nvidia.com>
Hi Slava,
> -----Original Message-----
> From: Slava Ovsiienko <viacheslavo@nvidia.com>
> Sent: Tuesday, October 12, 2021 11:06 AM
> To: dev@dpdk.org
> Subject: [PATCH v3 2/5] ethdev: fix missed experimental tag for modify field action
>
> EXPERIMENTAL tag was missed in rte_flow_action_modify_data structure description.
>
> Fixes: 73b68f4c54a0 ("ethdev: introduce generic modify flow action")
> Cc: stable@dpdk.org
>
> Signed-off-by: Viacheslav Ovsiienko <viacheslavo@nvidia.com>
> ---
> lib/ethdev/rte_flow.h | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/lib/ethdev/rte_flow.h b/lib/ethdev/rte_flow.h index f14f77772b..8a1eddd0b7 100644
> --- a/lib/ethdev/rte_flow.h
> +++ b/lib/ethdev/rte_flow.h
> @@ -3204,6 +3204,9 @@ enum rte_flow_field_id { };
>
> /**
> + * @warning
> + * @b EXPERIMENTAL: this structure may change without prior notice
> + *
> * Field description for MODIFY_FIELD action.
> */
> struct rte_flow_action_modify_data {
> --
> 2.18.1
Acked-by: Ori Kam <orika@nvidia.com>
Thanks,
Ori
next prev parent reply other threads:[~2021-10-12 8:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210910141609.8410-1-viacheslavo@nvidia.com>
2021-09-10 14:16 ` [dpdk-stable] [RFC 3/3] app/testpmd: fix hex string parser in flow commands Viacheslav Ovsiienko
[not found] ` <20211001195223.31909-1-viacheslavo@nvidia.com>
2021-10-01 19:52 ` [dpdk-stable] [PATCH " Viacheslav Ovsiienko
[not found] ` <20211010234547.1495-1-viacheslavo@nvidia.com>
2021-10-10 23:45 ` [dpdk-stable] [PATCH v2 3/5] " Viacheslav Ovsiienko
2021-10-11 9:15 ` Ori Kam
[not found] ` <20211012080631.28504-1-viacheslavo@nvidia.com>
2021-10-12 8:06 ` [dpdk-stable] [PATCH v3 2/5] ethdev: fix missed experimental tag for modify field action Viacheslav Ovsiienko
2021-10-12 8:13 ` Ori Kam [this message]
2021-10-12 8:14 ` [dpdk-stable] [dpdk-dev] " Andrew Rybchenko
2021-10-12 8:06 ` [dpdk-stable] [PATCH v3 4/5] app/testpmd: fix hex string parser in flow commands Viacheslav Ovsiienko
[not found] ` <20211012202557.30295-1-viacheslavo@nvidia.com>
2021-10-12 20:25 ` [dpdk-stable] [PATCH v5 2/5] ethdev: fix missed experimental tag for modify field action Viacheslav Ovsiienko
2021-10-12 20:25 ` [dpdk-stable] [PATCH v5 4/5] app/testpmd: fix hex string parser in flow commands Viacheslav Ovsiienko
[not found] ` <20211013184516.25338-1-viacheslavo@nvidia.com>
2021-10-13 18:45 ` [dpdk-stable] [PATCH v6 2/5] ethdev: fix missed experimental tag for modify field action Viacheslav Ovsiienko
2021-10-13 18:45 ` [dpdk-stable] [PATCH v6 4/5] app/testpmd: fix hex string parser in flow commands Viacheslav Ovsiienko
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=DM8PR12MB5400E4CE95A59DBD11AC5F5CD6B69@DM8PR12MB5400.namprd12.prod.outlook.com \
--to=orika@nvidia.com \
--cc=dev@dpdk.org \
--cc=getelson@nvidia.com \
--cc=matan@nvidia.com \
--cc=rasland@nvidia.com \
--cc=shahafs@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).