[dpdk-dev] [PATCH] usertools: fix pmdinfo parsing

2020-11-03 Thread David Marchand
This script was using the librte_pmd prefix has a filter to follow DT_NEEDED entries. Now that we changed the driver names, update this heuristic with an explicit list of device classes. Fixes: a20b2c01a7a1 ("build: standardize component names and defines") Signed-off-by: David Marchand --- use

Re: [dpdk-dev] [PATCH] usertools: fix pmdinfo parsing

2020-11-03 Thread Robin Jarry
2020-11-03, David Marchand: > This script was using the librte_pmd prefix has a filter to follow > DT_NEEDED entries. > Now that we changed the driver names, update this heuristic with an > explicit list of device classes. > > Fixes: a20b2c01a7a1 ("build: standardize component names and defines")

Re: [dpdk-dev] [PATCH] usertools: fix pmdinfo parsing

2020-11-03 Thread David Marchand
On Tue, Nov 3, 2020 at 8:27 PM Robin Jarry wrote: > 2020-11-03, David Marchand: > > This script was using the librte_pmd prefix has a filter to follow as* > > DT_NEEDED entries. > > Now that we changed the driver names, update this heuristic with an > > explicit list of device classes. > > > > F

Re: [dpdk-dev] [PATCH] usertools: fix pmdinfo parsing

2020-11-03 Thread Stephen Hemminger
On Tue, 3 Nov 2020 21:20:43 +0100 David Marchand wrote: > On Tue, Nov 3, 2020 at 8:27 PM Robin Jarry wrote: > > 2020-11-03, David Marchand: > > > This script was using the librte_pmd prefix has a filter to follow > > as* > > > > DT_NEEDED entries. > > > Now that we changed the driver names

Re: [dpdk-dev] [PATCH] usertools: fix pmdinfo parsing

2020-11-04 Thread Olivier Matz
On Tue, Nov 03, 2020 at 03:54:39PM -0800, Stephen Hemminger wrote: > On Tue, 3 Nov 2020 21:20:43 +0100 > David Marchand wrote: > > > On Tue, Nov 3, 2020 at 8:27 PM Robin Jarry wrote: > > > 2020-11-03, David Marchand: > > > > This script was using the librte_pmd prefix has a filter to follow

Re: [dpdk-dev] [PATCH] usertools: fix pmdinfo parsing

2020-11-04 Thread Robin Jarry
2020-11-03, David Marchand: > Less ugly with a regular expression? > > if re.match(r"^librte_(baseband|compress|crypto|event|net|raw|regex|vdpa)_", > force_unicode(tag.needed)): No, that's worse :D As Stephen said, maybe it would be more readable if the list of supported classes were