From: Thomas Monjalon <thomas@monjalon.net>
To: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>,
Ori Kam <orika@nvidia.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, Ferruh Yigit <ferruh.yigit@amd.com>
Subject: Re: [PATCH 0/2] update ethdev deprecation notices
Date: Fri, 25 Nov 2022 11:00:31 +0100 [thread overview]
Message-ID: <2481759.4XsnlVU6TS@thomas> (raw)
In-Reply-To: <MW2PR12MB4666CA7D77589A88B12E2336D60F9@MW2PR12MB4666.namprd12.prod.outlook.com>
> > > The deprecation plan was not followed for rte_flow actions and items.
> > > It needs to be reflected before the release 22.11.
> > >
> > > Thomas Monjalon (2):
> > > doc: update deprecation notice of legacy flow actions
> > > doc: update deprecation notice of flow items
> >
> > Series-acked-by: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
>
> Series-acked-by: Ori Kam <orika@nvidia.com>
Applied
prev parent reply other threads:[~2022-11-25 10:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-24 14:26 Thomas Monjalon
2022-11-24 14:26 ` [PATCH 1/2] doc: update deprecation notice of legacy flow actions Thomas Monjalon
2022-11-24 14:26 ` [PATCH 2/2] doc: update deprecation notice of flow items Thomas Monjalon
2022-11-24 14:35 ` [PATCH 0/2] update ethdev deprecation notices Andrew Rybchenko
2022-11-24 14:36 ` Ori Kam
2022-11-25 10:00 ` Thomas Monjalon [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=2481759.4XsnlVU6TS@thomas \
--to=thomas@monjalon.net \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@amd.com \
--cc=orika@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).