From: Thomas Monjalon <thomas@monjalon.net>
To: David Marchand <david.marchand@redhat.com>
Cc: dev@dpdk.org, ferruh.yigit@amd.com,
konstantin.v.ananyev@yandex.ru, john.mcnamara@intel.com,
bruce.richardson@intel.com, stephen@networkplumber.org
Subject: Re: [PATCH] flow_classify: mark library as deprecated
Date: Thu, 27 Oct 2022 16:14:40 +0200 [thread overview]
Message-ID: <37885061.10thIPus4b@thomas> (raw)
In-Reply-To: <20221027094655.1007047-1-david.marchand@redhat.com>
27/10/2022 11:46, David Marchand:
> This library has no maintainer and, for now, nobody expressed interest
> in taking over.
> Mark this experimental library as deprecated and announce plan for
> removal in v23.11.
>
> Signed-off-by: David Marchand <david.marchand@redhat.com>
It adds enough warnings to reach potential users.
Acked-by: Thomas Monjalon <thomas@monjalon.net>
next prev parent reply other threads:[~2022-10-27 14:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-27 9:46 David Marchand
2022-10-27 10:31 ` Ferruh Yigit
2022-10-27 12:44 ` Konstantin Ananyev
2022-10-27 14:14 ` Thomas Monjalon [this message]
2022-10-28 14:12 ` David Marchand
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=37885061.10thIPus4b@thomas \
--to=thomas@monjalon.net \
--cc=bruce.richardson@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@amd.com \
--cc=john.mcnamara@intel.com \
--cc=konstantin.v.ananyev@yandex.ru \
--cc=stephen@networkplumber.org \
/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).