DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Wu, Jingjing" <jingjing.wu@intel.com>
To: Stephen Hemminger <stephen@networkplumber.org>,
	"dev@dpdk.org" <dev@dpdk.org>
Cc: Stephen Hemminger <sthemmin@microsoft.com>
Subject: Re: [dpdk-dev] [PATCH 2/6] i40e: don't refer to eth_dev->pci_dev
Date: Fri, 6 Jan 2017 01:50:33 +0000	[thread overview]
Message-ID: <9BB6961774997848B5B42BEC655768F810CC3EFE@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <20170102230850.32610-3-sthemmin@microsoft.com>



> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Stephen Hemminger
> Sent: Tuesday, January 3, 2017 7:09 AM
> To: dev@dpdk.org
> Cc: Stephen Hemminger <sthemmin@microsoft.com>
> Subject: [dpdk-dev] [PATCH 2/6] i40e: don't refer to eth_dev->pci_dev
> 
> Later patches remove pci_dev from the ethernet device structure.
> Fix the i40e code to just use it's own name when forming zone name.
> 
> Signed-off-by: Stephen Hemminger <sthemmin@microsoft.com>

Acked-by: Jingjing Wu <jingjing.wu@intel.com>

  reply	other threads:[~2017-01-06  1:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-02 23:08 [dpdk-dev] [PATCH 0/6] VMBUS and driver infrastructure Stephen Hemminger
2017-01-02 23:08 ` [dpdk-dev] [PATCH 1/6] ethdev: increase length ethernet device internal name Stephen Hemminger
2017-01-02 23:08 ` [dpdk-dev] [PATCH 2/6] i40e: don't refer to eth_dev->pci_dev Stephen Hemminger
2017-01-06  1:50   ` Wu, Jingjing [this message]
2017-01-02 23:08 ` [dpdk-dev] [PATCH 3/6] vmxnet3: " Stephen Hemminger
2017-01-02 23:08 ` [dpdk-dev] [PATCH 4/6] cxgbe: " Stephen Hemminger
2017-01-02 23:08 ` [dpdk-dev] [PATCH 5/6] ethdev: break ethernet driver and pci_driver connection Stephen Hemminger
2017-01-02 23:08 ` [dpdk-dev] [PATCH 6/6] eal: VMBUS infrastructure Stephen Hemminger

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=9BB6961774997848B5B42BEC655768F810CC3EFE@SHSMSX103.ccr.corp.intel.com \
    --to=jingjing.wu@intel.com \
    --cc=dev@dpdk.org \
    --cc=stephen@networkplumber.org \
    --cc=sthemmin@microsoft.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).