DPDK patches and discussions
 help / color / mirror / Atom feed
From: Maciej Gajdzica <maciejx.t.gajdzica@intel.com>
To: dev@dpdk.org
Subject: [dpdk-dev] [PATCH 4/4] vmxnet3: Updated comments.
Date: Mon, 30 Jun 2014 10:22:44 +0100	[thread overview]
Message-ID: <1404120164-18712-5-git-send-email-maciejx.t.gajdzica@intel.com> (raw)
In-Reply-To: <1404120164-18712-1-git-send-email-maciejx.t.gajdzica@intel.com>

Signed-off-by: Maciej Gajdzica <maciejx.t.gajdzica@intel.com>
---
 lib/librte_eal/common/include/rte_pci_dev_ids.h | 9 +++++----
 1 file changed, 5 insertions(+), 4 deletions(-)

diff --git a/lib/librte_eal/common/include/rte_pci_dev_ids.h b/lib/librte_eal/common/include/rte_pci_dev_ids.h
index 9c1ee04..b0737a5 100644
--- a/lib/librte_eal/common/include/rte_pci_dev_ids.h
+++ b/lib/librte_eal/common/include/rte_pci_dev_ids.h
@@ -63,17 +63,18 @@
  * This file contains a list of the PCI device IDs recognised by DPDK, which
  * can be used to fill out an array of structures describing the devices.
  *
- * Currently four families of devices are recognised: those supported by the
+ * Currently five families of devices are recognised: those supported by the
  * IGB driver, by EM driver, those supported by the IXGBE driver, and by virtio
- * driver which is a para virtualization driver running in guest virtual machine.
- * The inclusion of these in an array built using this file depends on the
- * definition of
+ * and vmxnet3 drivers which are para virtualization drivers running in guest
+ * virtual machine. The inclusion of these in an array built using this file 
+ * depends on the definition of
  * RTE_PCI_DEV_ID_DECL_EM
  * RTE_PCI_DEV_ID_DECL_IGB
  * RTE_PCI_DEV_ID_DECL_IGBVF
  * RTE_PCI_DEV_ID_DECL_IXGBE
  * RTE_PCI_DEV_ID_DECL_IXGBEVF
  * RTE_PCI_DEV_ID_DECL_VIRTIO
+ * RTE_PCI_DEV_ID_DECL_VMXNET3
  * at the time when this file is included.
  *
  * In order to populate an array, the user of this file must define this macro:
-- 
2.0.0

      parent reply	other threads:[~2014-06-30  9:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-30  9:22 [dpdk-dev] [PATCH 0/4] VMXNET3 support for FreeBSD Maciej Gajdzica
2014-06-30  9:22 ` [dpdk-dev] [PATCH 1/4] vmxnet3: Removed unused include that broke VMXNET3 driver compilation under FreeBSD Maciej Gajdzica
2014-06-30  9:22 ` [dpdk-dev] [PATCH 2/4] vmxnet3: Added makefile entries to compile VMXNET3 driver " Maciej Gajdzica
2014-06-30  9:22 ` [dpdk-dev] [PATCH 3/4] vmxnet3: Added macro adding VMXNET3 to the list of recognized PCI devices Maciej Gajdzica
2014-06-30  9:22 ` Maciej Gajdzica [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=1404120164-18712-5-git-send-email-maciejx.t.gajdzica@intel.com \
    --to=maciejx.t.gajdzica@intel.com \
    --cc=dev@dpdk.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 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).