DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Pablo de Lara <pablo.de.lara.guarch@intel.com>
Cc: Neil Horman <nhorman@tuxdriver.com>, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH 0/5] Driver register fixes
Date: Sat, 09 Jul 2016 23:53:46 +0200	[thread overview]
Message-ID: <1798743.vPHiBmbf43@xps13> (raw)
In-Reply-To: <20160709134520.GB21705@neilslaptop.think-freely.org>

2016-07-09 09:45, Neil Horman:
> 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
> > 
> Series
> Acked-by: Neil Horman <nhorman@tuxdriver.com>

Applied, thanks

      reply	other threads:[~2016-07-09 21:53 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 ` [dpdk-dev] [PATCH 0/5] Driver register fixes Neil Horman
2016-07-09 21:53   ` 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=1798743.vPHiBmbf43@xps13 \
    --to=thomas.monjalon@6wind.com \
    --cc=dev@dpdk.org \
    --cc=nhorman@tuxdriver.com \
    --cc=pablo.de.lara.guarch@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).