DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Kumara Parameshwaran <kumaraparamesh92@gmail.com>, <dev@dpdk.org>
Cc: Kumara Parameshwaran <kparameshwar@vmware.com>
Subject: Re: [PATCH v1] drivers/net: use internal API to get eth dev from name
Date: Thu, 3 Feb 2022 12:31:07 +0000	[thread overview]
Message-ID: <a8aa8041-5b3a-b0ed-8e09-e6280352e28b@intel.com> (raw)
In-Reply-To: <20220203082412.79028-1-kumaraparamesh92@gmail.com>

On 2/3/2022 8:24 AM, Kumara Parameshwaran wrote:
> From: Kumara Parameshwaran <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>
> ---
> v1
> * Replace rte_eth_get_get_port_by_name in PMDs with rte_eth_dev_get_by_name
>    where port_id is used to retrieve rte_eth_dev data structure
> 

Hi Kumara, Thanks for the work.

Reviewed-by: Ferruh Yigit <ferruh.yigit@intel.com>


  parent reply	other threads:[~2022-02-03 12:31 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-03  8:24 Kumara Parameshwaran
2022-02-03 11:09 ` kumaraparameshwaran rathinavel
2022-02-03 11:31   ` Ferruh Yigit
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
2022-02-03 12:31 ` Ferruh Yigit [this message]
2022-02-04 13:46   ` Ferruh Yigit
2022-02-03 12:34 ` Ferruh Yigit
2022-02-03 12:35 ` Ferruh Yigit
2022-02-04  9:51   ` Singh, Jasvinder

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=a8aa8041-5b3a-b0ed-8e09-e6280352e28b@intel.com \
    --to=ferruh.yigit@intel.com \
    --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).