All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Ferruh Yigit <ferruh.yigit@intel.com>
Cc: dev@dpdk.org, Gaetan Rivet <gaetan.rivet@6wind.com>,
	Jan Blunck <jblunck@infradead.org>
Subject: Re: [PATCH v2 3/3] ethdev: use device name from device structure
Date: Thu, 06 Jul 2017 00:11:21 +0200	[thread overview]
Message-ID: <3994424.RAXfEQKQeg@xps> (raw)
In-Reply-To: <20170609183606.34596-3-ferruh.yigit@intel.com>

09/06/2017 20:36, Ferruh Yigit:
> Device name resides in two different locations, in rte_device->name and
> in ethernet device private data.
> 
> For now, the copy in the ethernet device private data is required for
> multi process support, the name is the how secondary process finds about
> primary process device.
> 
> But in the ethdev library some eth_dev->data->name usage can be
> converted to rte_device->name.
> 
> This patch updates ethdev to use rte_device->name when possible.
> 
> Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com>

Series applied, thanks

      reply	other threads:[~2017-07-05 22:11 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-26 16:11 [PATCH 1/2] ethdev: ensure same name size for device and ethdev Ferruh Yigit
2017-05-26 16:11 ` [PATCH 2/2] drivers/net: use device name from device structure Ferruh Yigit
2017-06-09 13:52   ` Thomas Monjalon
2017-06-09 14:16     ` Ferruh Yigit
2017-06-10  7:35     ` Jan Blunck
2017-06-12  8:57       ` Ferruh Yigit
2017-06-09 18:36 ` [PATCH v2 1/3] ethdev: ensure same name size for device and ethdev Ferruh Yigit
2017-06-09 18:36   ` [PATCH v2 2/3] drivers/net: use device name from device structure Ferruh Yigit
2017-06-09 18:36   ` [PATCH v2 3/3] ethdev: " Ferruh Yigit
2017-07-05 22:11     ` Thomas Monjalon [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=3994424.RAXfEQKQeg@xps \
    --to=thomas@monjalon.net \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=gaetan.rivet@6wind.com \
    --cc=jblunck@infradead.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.