DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Gaetan Rivet <gaetan.rivet@6wind.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v3 3/3] vdev: use standard bus registration function
Date: Wed, 21 Jun 2017 16:41:24 +0200	[thread overview]
Message-ID: <8812794.vYtIgvyNPj@xps> (raw)
In-Reply-To: <644a3ea058797563976718beeae8f4e7eda5be3c.1496876926.git.gaetan.rivet@6wind.com>

08/06/2017 01:58, Gaetan Rivet:
> +RTE_REGISTER_BUS(VIRTUAL_BUS_NAME, rte_vdev_bus);

nice :)

      reply	other threads:[~2017-06-21 14:41 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-24 15:18 [dpdk-dev] [PATCH 0/3] eal: complete attach / detach support Gaetan Rivet
2017-05-24 15:18 ` [dpdk-dev] [PATCH 1/3] pci: implement attach/detach bus operation Gaetan Rivet
2017-05-24 15:18 ` [dpdk-dev] [PATCH 2/3] vdev: implement attach " Gaetan Rivet
2017-05-24 15:18 ` [dpdk-dev] [PATCH 3/3] vdev: use standard bus registration function Gaetan Rivet
2017-06-01 10:11 ` [dpdk-dev] [PATCH v2 0/3] eal: complete attach / detach support Gaetan Rivet
2017-06-01 10:12   ` [dpdk-dev] [PATCH v2 1/3] pci: implement plug/unplug bus operation Gaetan Rivet
2017-06-01 10:12   ` [dpdk-dev] [PATCH v2 2/3] dev: remove vdev function dependency Gaetan Rivet
2017-06-01 10:12   ` [dpdk-dev] [PATCH v2 3/3] vdev: use standard bus registration function Gaetan Rivet
2017-06-07 23:58   ` [dpdk-dev] [PATCH v3 0/3] eal: complete attach / detach support Gaetan Rivet
2017-06-07 23:58     ` [dpdk-dev] [PATCH v3 1/3] pci: implement hotplug bus operation Gaetan Rivet
2017-06-07 23:58     ` [dpdk-dev] [PATCH v3 2/3] dev: remove vdev function dependency Gaetan Rivet
2017-06-21 14:42       ` Thomas Monjalon
2017-06-07 23:58     ` [dpdk-dev] [PATCH v3 3/3] vdev: use standard bus registration function Gaetan Rivet
2017-06-21 14:41       ` 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=8812794.vYtIgvyNPj@xps \
    --to=thomas@monjalon.net \
    --cc=dev@dpdk.org \
    --cc=gaetan.rivet@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).