DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Vipin Varghese <vipin.varghese@intel.com>,
	dev@dpdk.org, john.mcnamara@intel.com, deepak.k.jain@intel.com
Subject: Re: [dpdk-dev] [PATCH v2] ethdev: update description for functions
Date: Mon, 21 May 2018 16:16:31 +0100	[thread overview]
Message-ID: <3f4bb784-df27-7f74-be83-1881fce460a8@intel.com> (raw)
In-Reply-To: <6fde75eb-3719-84ed-b773-cbb652471343@intel.com>

On 5/21/2018 4:15 PM, Ferruh Yigit wrote:
> On 5/18/2018 6:12 AM, Vipin Varghese wrote:
>> Change adds extra information on name parameter for API
>> rte_eth_dev_get_name_by_port and rte_eth_dev_get_port_by_name.
>>
>> Signed-off-by: Vipin Varghese <vipin.varghese@intel.com>
> 
> Reviewed-by: Ferruh Yigit <ferruh.yigit@intel.com>

Applied to dpdk-next-net/master, thanks.

      reply	other threads:[~2018-05-21 15:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-17 10:59 [dpdk-dev] [PATCH] " Vipin Varghese
2018-05-17 12:32 ` Ferruh Yigit
2018-05-18  5:03   ` Varghese, Vipin
2018-05-18  5:12 ` [dpdk-dev] [PATCH v2] " Vipin Varghese
2018-05-21 15:15   ` Ferruh Yigit
2018-05-21 15:16     ` Ferruh Yigit [this message]

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=3f4bb784-df27-7f74-be83-1881fce460a8@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=deepak.k.jain@intel.com \
    --cc=dev@dpdk.org \
    --cc=john.mcnamara@intel.com \
    --cc=vipin.varghese@intel.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).