From: Thomas Monjalon <thomas@monjalon.net>
To: Stephen Hemminger <stephen@networkplumber.org>, techboard@dpdk.org
Cc: David Marchand <david.marchand@redhat.com>,
techboard@dpdk.org, dev <dev@dpdk.org>,
Luca Boccassi <bluca@debian.org>,
"Mcnamara, John" <john.mcnamara@intel.com>,
Thomas Monjalon <thomas@monjalon.net>
Subject: Re: [dpdk-dev] [dpdk-techboard] [PATCH v3 00/10] rename blacklist/whitelist to block/allow
Date: Tue, 22 Sep 2020 18:18:02 +0200 [thread overview]
Message-ID: <33429326.yKmoO7Tkig@thomas> (raw)
In-Reply-To: <8969299.nXlkhJugru@thomas>
22/09/2020 18:16, Thomas Monjalon:
> 22/09/2020 16:28, Stephen Hemminger:
> > On Wed, 15 Jul 2020 12:01:27 +0200
> > Thomas Monjalon <thomas@monjalon.net> wrote:
> >
> > > 14/07/2020 07:33, Stephen Hemminger:
> > > > On Fri, 10 Jul 2020 17:06:11 +0200
> > > > David Marchand <david.marchand@redhat.com> wrote:
> > > >
> > > > > About deprecating existing API/EAL flags in this release, this should
> > > > > go through the standard deprecation process.
> > > > > I would go with introducing new options + full compatibility + a
> > > > > deprecation notice in the 20.08 release.
> > > > > The actual deprecation/API flagging will go in 20.11.
> > > > > Removal will come later.
> > > >
> > > > Like Make deprecation for 20.08 will leave the flags but add nag.
> > > > Want to make full removal in 20.11. Otherwise it will end up being 21.11
> > > > which is too far out.
> > >
> > > Excuse me I may lack a bit of context.
> > > Are you asking for removing some EAL options without following
> > > the deprecation process?
> >
> > These were in the 20.08 deprecation notice.
>
> Do you mean this?
> "
> The ``master-lcore`` argument to testpmd will be replaced
> with ``initial-lcore``. The old ``master-lcore`` argument
> will produce a runtime notification in 20.11 release, and
> be removed completely in a future release.
> "
For completeness, I see this as well:
"
The command line arguments to ``rte_eal_init`` will change from
``-b, --pci-blacklist`` to ``-x, --exclude`` and
``-w, --pci-whitelist`` to ``-i, --include``.
The old command line arguments will continue to be accepted in 20.11
but will cause a runtime warning message. The old arguments will
be removed in a future release.
"
next prev parent reply other threads:[~2020-09-22 16:18 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-13 0:00 [dpdk-dev] " Stephen Hemminger
2020-06-13 0:00 ` [dpdk-dev] [PATCH v3 01/10] rte_ethdev: change comment to rte_dev_eth_mac_addr_add Stephen Hemminger
2020-06-13 0:00 ` [dpdk-dev] [PATCH v3 02/10] mk: replace reference to blacklist/whitelist Stephen Hemminger
2020-06-13 0:00 ` [dpdk-dev] [PATCH v3 03/10] check_maintainers: change variable names Stephen Hemminger
2020-07-10 17:01 ` Thomas Monjalon
2020-06-13 0:00 ` [dpdk-dev] [PATCH v3 04/10] eal: replace usage of blacklist/whitelist in enum Stephen Hemminger
2020-06-13 0:00 ` [dpdk-dev] [PATCH v3 05/10] drivers: replace references to blacklist Stephen Hemminger
2020-06-15 6:32 ` Hemant Agrawal
2020-06-13 0:00 ` [dpdk-dev] [PATCH v3 06/10] eal: replace pci-whitelist/pci-blacklist options Stephen Hemminger
2020-06-13 0:00 ` [dpdk-dev] [PATCH v3 07/10] doc: replace references to blacklist/whitelist Stephen Hemminger
2020-06-13 0:00 ` [dpdk-dev] [PATCH v3 08/10] app/test: use new allowlist and blocklist Stephen Hemminger
2020-06-13 0:00 ` [dpdk-dev] [PATCH v3 09/10] doc: add note about blacklist/whitelist changes Stephen Hemminger
2020-06-13 0:00 ` [dpdk-dev] [PATCH v3 10/10] eal: mark old macros for blacklist/whitelist as deprecated Stephen Hemminger
2020-06-17 12:05 ` [dpdk-dev] [PATCH v3 00/10] rename blacklist/whitelist to block/allow Mcnamara, John
2020-07-10 15:06 ` David Marchand
2020-07-14 4:43 ` Stephen Hemminger
2020-07-14 5:33 ` Stephen Hemminger
2020-07-15 10:01 ` [dpdk-dev] [dpdk-techboard] " Thomas Monjalon
2020-09-22 14:28 ` Stephen Hemminger
2020-09-22 16:16 ` Thomas Monjalon
2020-09-22 16:18 ` Thomas Monjalon [this message]
2020-09-22 17:12 ` Stephen Hemminger
2020-07-14 5:39 ` [dpdk-dev] [PATCH v4 00/11] rename blacklist/whitelist to exclude/include Stephen Hemminger
2020-07-14 5:39 ` [dpdk-dev] [PATCH v4 01/11] rte_ethdev: change comment to rte_dev_eth_mac_addr_add Stephen Hemminger
2020-07-14 5:39 ` [dpdk-dev] [PATCH v4 02/11] mk: replace reference to blacklist/whitelist Stephen Hemminger
2020-07-14 5:39 ` [dpdk-dev] [PATCH v4 03/11] check_maintainers: change variable names Stephen Hemminger
2020-07-14 5:39 ` [dpdk-dev] [PATCH v4 04/11] eal: replace usage of blacklist/whitelist in enum Stephen Hemminger
2020-07-14 5:39 ` [dpdk-dev] [PATCH v4 05/11] drivers: replace references to blacklist Stephen Hemminger
2020-07-14 5:39 ` [dpdk-dev] [PATCH v4 06/11] eal: replace pci-whitelist/pci-blacklist options Stephen Hemminger
2020-07-14 5:39 ` [dpdk-dev] [PATCH v4 07/11] doc: replace references to blacklist/whitelist Stephen Hemminger
2020-07-14 5:39 ` [dpdk-dev] [PATCH v4 08/11] app/test: use new allowlist and blocklist Stephen Hemminger
2020-07-14 5:39 ` [dpdk-dev] [PATCH v4 09/11] doc: add note about blacklist/whitelist changes Stephen Hemminger
2020-07-14 5:39 ` [dpdk-dev] [PATCH v4 10/11] eal: mark old macros for blacklist/whitelist as deprecated Stephen Hemminger
2020-07-14 5:39 ` [dpdk-dev] [PATCH v4 11/11] doc: update examples to new config options Stephen Hemminger
2020-07-14 6:05 ` [dpdk-dev] [PATCH v4 00/11] rename blacklist/whitelist to exclude/include Stephen Hemminger
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=33429326.yKmoO7Tkig@thomas \
--to=thomas@monjalon.net \
--cc=bluca@debian.org \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=john.mcnamara@intel.com \
--cc=stephen@networkplumber.org \
--cc=techboard@dpdk.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).