From: Ferruh Yigit <ferruh.yigit@intel.com>
To: kumaraparameshwaran rathinavel <kumaraparamesh92@gmail.com>,
<dev@dpdk.org>
Cc: Kumara Parameshwaran <kparameshwar@vmware.com>,
"ci@dpdk.org" <ci@dpdk.org>, Ali Alnubani <alialnu@nvidia.com>
Subject: Re: [PATCH v1] drivers/net: use internal API to get eth dev from name
Date: Thu, 3 Feb 2022 11:31:34 +0000 [thread overview]
Message-ID: <f92710d2-fd3d-897e-1103-7325749c5c8a@intel.com> (raw)
In-Reply-To: <CANxNyatu+tyqf1gyxM_1P_=oCyNiEOMdpbWSMLOnhgiffAnQGw@mail.gmail.com>
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.
Meanwhile I re-run the community lab tests on top of next-net repo,
still some other checks, like Intel ones, will continue to fail until
patches reach to main tree.
> On Thu, Feb 3, 2022 at 1:54 PM Kumara Parameshwaran <kumaraparamesh92@gmail.com <mailto:kumaraparamesh92@gmail.com>> wrote:
>
> From: Kumara Parameshwaran <kparameshwar@vmware.com <mailto:kparameshwar@vmware.com>>
>
> Make changes in PMDs to use the new function where
> rte_eth_dev_get_port_by_name is used to get port_id
> to access rte_eth_devices
>
> Signed-off-by: Kumara Parameshwaran <kparameshwar@vmware.com <mailto:kparameshwar@vmware.com>>
next parent reply other threads:[~2022-02-03 11:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220203082412.79028-1-kumaraparamesh92@gmail.com>
[not found] ` <CANxNyatu+tyqf1gyxM_1P_=oCyNiEOMdpbWSMLOnhgiffAnQGw@mail.gmail.com>
2022-02-03 11:31 ` Ferruh Yigit [this message]
2022-02-07 16:08 ` Ali Alnubani
2022-02-07 16:36 ` Ferruh Yigit
2022-02-07 16:47 ` Ali Alnubani
2022-02-07 17:25 ` Ferruh Yigit
2022-02-07 19:58 ` Owen Hilyard
2022-02-10 20:44 ` Yigit, Ferruh
2022-02-10 22:06 ` Owen Hilyard
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=f92710d2-fd3d-897e-1103-7325749c5c8a@intel.com \
--to=ferruh.yigit@intel.com \
--cc=alialnu@nvidia.com \
--cc=ci@dpdk.org \
--cc=dev@dpdk.org \
--cc=kparameshwar@vmware.com \
--cc=kumaraparamesh92@gmail.com \
/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).