[dpdk-dev] [dpdk-techboard] [PATCH v3 00/10] rename blacklist/whitelist to block/allow

[Thomas Monjalon]

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 at monjalon.net> wrote:
> > 
> > > 14/07/2020 07:33, Stephen Hemminger:
> > > > On Fri, 10 Jul 2020 17:06:11 +0200
> > > > David Marchand <david.marchand at 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.
"