RE: [PATCH v1] drivers/net: use internal API to get eth dev from name

[Ali Alnubani <alialnu@nvidia.com>]

> -----Original Message-----
> From: Ferruh Yigit <ferruh.yigit@intel.com>
> Sent: Thursday, February 3, 2022 1:32 PM
> To: kumaraparameshwaran rathinavel <kumaraparamesh92@gmail.com>;
> dev@dpdk.org
> Cc: Kumara Parameshwaran <kparameshwar@vmware.com>; ci@dpdk.org;
> Ali Alnubani <alialnu@nvidia.com>
> Subject: Re: [PATCH v1] drivers/net: use internal API to get eth dev from
> name
> 
> On 2/3/2022 11:09 AM, kumaraparameshwaran rathinavel wrote:
> > Ferruh,
> >
> > Since in the older patch we had introduced rte_eth_dev_get_by_name
> patch and had been merged to dpdk-next-net, the current patch failed for
> the build when I submitted the patch. Is there a way to enforce it to dpdk-
> next-net ?
> >
> 
> CIs apply it onto the main repo, there is a script that chose which
> tree to apply, it seems it is not working as expected for the
> 'drivers/net:' case, cc'ed ci mail list and @Ali for it.
> 

Sorry for the delayed response,

The script (https://git.dpdk.org/tools/dpdk-ci/tree/tools/pw_maintainers_cli.py) correctly chooses next-net for this patch:
$ MAINTAINERS_FILE_PATH=/path/to/MAINTAINERS tools/pw_maintainers_cli.py --type patch list-trees 106830
Output: dpdk-next-net

Did the script fail for some reason during this build?