DPDK patches and discussions
 help / color / mirror / Atom feed
From: Neil Horman <nhorman@tuxdriver.com>
To: Pablo de Lara <pablo.de.lara.guarch@intel.com>
Cc: dev@dpdk.org, thomas.monjalon@6wind.com
Subject: Re: [dpdk-dev] [PATCH 0/5] Driver register fixes
Date: Sat, 9 Jul 2016 09:45:20 -0400	[thread overview]
Message-ID: <20160709134520.GB21705@neilslaptop.think-freely.org> (raw)
In-Reply-To: <1468026374-28042-1-git-send-email-pablo.de.lara.guarch@intel.com>

On Sat, Jul 09, 2016 at 02:06:09AM +0100, Pablo de Lara wrote:
> This patchset makes some extra changes after the modification
> of the PMD_REGISTER_DRIVER macro, including renaming back
> some virtual device driver names (virtio could not be renamed)
> and fixing/adding arguments of some drivers. 
> 
> Pablo de Lara (5):
>   drivers: revert vdev driver names to original
>   drivers: remove static driver names
>   drivers: split driver arguments in multiple lines
>   drivers: add missing virtio and xenvirt arguments
>   net/bonding: fix range of mode argument
> 
>  drivers/crypto/aesni_gcm/aesni_gcm_pmd.c   |  6 ++++--
>  drivers/crypto/aesni_mb/rte_aesni_mb_pmd.c |  6 ++++--
>  drivers/crypto/kasumi/rte_kasumi_pmd.c     |  6 ++++--
>  drivers/crypto/null/null_crypto_pmd.c      |  6 ++++--
>  drivers/crypto/snow3g/rte_snow3g_pmd.c     |  6 ++++--
>  drivers/net/af_packet/rte_eth_af_packet.c  |  9 ++++++---
>  drivers/net/bnxt/bnxt_ethdev.c             |  1 -
>  drivers/net/bonding/rte_eth_bond_pmd.c     | 19 ++++++++++++-------
>  drivers/net/cxgbe/cxgbe_ethdev.c           |  1 -
>  drivers/net/ena/ena_ethdev.c               |  1 -
>  drivers/net/mlx4/mlx4.c                    |  1 -
>  drivers/net/mlx5/mlx5.c                    |  1 -
>  drivers/net/mpipe/mpipe_tilegx.c           |  6 ++----
>  drivers/net/null/rte_eth_null.c            |  5 +++--
>  drivers/net/pcap/rte_eth_pcap.c            | 11 +++++++----
>  drivers/net/ring/rte_eth_ring.c            |  4 ++--
>  drivers/net/szedata2/rte_eth_szedata2.c    |  7 +++----
>  drivers/net/thunderx/nicvf_ethdev.c        |  1 -
>  drivers/net/vhost/rte_eth_vhost.c          |  5 +++--
>  drivers/net/virtio/virtio_user_ethdev.c    |  7 ++++++-
>  drivers/net/xenvirt/rte_eth_xenvirt.c      |  5 +++--
>  21 files changed, 67 insertions(+), 47 deletions(-)
> 
> -- 
> 2.7.4
> 
> 
Series
Acked-by: Neil Horman <nhorman@tuxdriver.com>

  parent reply	other threads:[~2016-07-09 13:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-09  1:06 Pablo de Lara
2016-07-09  1:06 ` [dpdk-dev] [PATCH 1/5] drivers: revert vdev driver names to original Pablo de Lara
2016-07-09  1:06 ` [dpdk-dev] [PATCH 2/5] drivers: remove static driver names Pablo de Lara
2016-07-09  1:06 ` [dpdk-dev] [PATCH 3/5] drivers: split driver arguments in multiple lines Pablo de Lara
2016-07-09  1:06 ` [dpdk-dev] [PATCH 4/5] drivers: add missing virtio and xenvirt arguments Pablo de Lara
2016-07-09  1:06 ` [dpdk-dev] [PATCH 5/5] net/bonding: fix range of mode argument Pablo de Lara
2016-07-09 13:45 ` Neil Horman [this message]
2016-07-09 21:53   ` [dpdk-dev] [PATCH 0/5] Driver register fixes 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=20160709134520.GB21705@neilslaptop.think-freely.org \
    --to=nhorman@tuxdriver.com \
    --cc=dev@dpdk.org \
    --cc=pablo.de.lara.guarch@intel.com \
    --cc=thomas.monjalon@6wind.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).