DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: "Zhang, Helin" <helin.zhang@intel.com>
Cc: "Wu, Jingjing" <jingjing.wu@intel.com>, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] i40e: move PCI device ids to driver
Date: Mon, 11 Jul 2016 08:55:24 +0200	[thread overview]
Message-ID: <2755332.bbWM3o0Z6X@xps13> (raw)
In-Reply-To: <F35DEAC7BCE34641BA9FAC6BCA4A12E717D953B3@SHSMSX103.ccr.corp.intel.com>

Hi Helin,

2016-07-11 06:19, Zhang, Helin:
> Hi Jingjing
> 
> I'd suggest to add a new header file in each PMD to define what we defined in rte_pci_dev_ids.h.

Why?

> There was a patch set submitted several months ago, like that.

Which one?

  reply	other threads:[~2016-07-11  6:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-11  4:01 Jingjing Wu
2016-07-11  6:19 ` Zhang, Helin
2016-07-11  6:55   ` Thomas Monjalon [this message]
2016-07-11  7:02     ` Zhang, Helin
2016-07-11  7:29       ` Wu, Jingjing
2016-07-11  8:31         ` Zhang, Helin
2016-07-11 16:31 ` Thomas Monjalon

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=2755332.bbWM3o0Z6X@xps13 \
    --to=thomas.monjalon@6wind.com \
    --cc=dev@dpdk.org \
    --cc=helin.zhang@intel.com \
    --cc=jingjing.wu@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).