DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Bernard Iremonger <bernard.iremonger@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v7 00/28] remove pci driver from vdevs
Date: Fri, 30 Oct 2015 16:21:34 +0100	[thread overview]
Message-ID: <1777159.x2ndGBQgqJ@xps13> (raw)
In-Reply-To: <1446217733-9887-1-git-send-email-bernard.iremonger@intel.com>

2015-10-30 15:08, Bernard Iremonger:
> Changes in v7:
> rebase to latest code.

Please Bernard, be kind and change the status of your previous patchset.
I'm tired to do it for 28 patches each time you rebase.
By the way, it is not needed to do a patch per driver when it is the
same oneliner without any explanation message.

> Bernard Iremonger (28):
>   librte_eal: add RTE_KDRV_NONE for vdevs
>   librte_ether: add fields from rte_pci_driver to rte_eth_dev_data
>   librte_ether: add function rte_eth_copy_dev_info
>   ixgbe: copy pci device info to eth_dev data
>   e1000: copy pci device info to eth_dev data
>   i40e: copy pci device info to eth_dev data
>   fm10k: copy pci device info to eth_dev data
>   bnx2x: copy pci device info to eth_dev data
>   cxgbe: copy pci device info to eth_dev data
>   enic: copy pci device info to eth_dev data
>   mlx4: copy pci device info to eth_dev data
>   virtio: copy pci device info to eth_dev data
>   vmxnet3: copy pci device info to eth_dev data
>   null: copy device info to eth_dev data
>   ring: copy device info to eth_dev data
>   pcap: copy device info to eth_dev data
>   af_packet: copy device info to eth_dev data
>   xenvirt: copy device info to eth_dev data
>   mpipe: copy device info to eth_dev data
>   bonding: copy device info to eth_dev data
>   librte_ether: remove branches on pci_dev
>   null: remove pci device
>   ring: remove pci device
>   pcap: remove pci device
>   af_packet: remove pci device
>   xenvirt: remove pci device
>   mpipe: remove pci device
>   bonding: remove pci device

  parent reply	other threads:[~2015-10-30 15:22 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <PATCH v7>
2015-10-30 15:08 ` Bernard Iremonger
2015-10-30 15:08   ` [dpdk-dev] [PATCH v7 01/28] librte_eal: add RTE_KDRV_NONE for vdevs Bernard Iremonger
2015-10-30 15:08   ` [dpdk-dev] [PATCH v7 02/28] librte_ether: add fields from rte_pci_driver to rte_eth_dev_data Bernard Iremonger
2015-11-01 21:12     ` Thomas Monjalon
2015-11-02 10:36       ` Iremonger, Bernard
2015-11-02 16:32         ` Thomas Monjalon
2015-11-02 16:44           ` Iremonger, Bernard
2015-11-02 17:42             ` Thomas Monjalon
2015-11-01 21:41     ` Thomas Monjalon
2015-11-02 10:33       ` Iremonger, Bernard
2015-10-30 15:08   ` [dpdk-dev] [PATCH v7 03/28] librte_ether: add function rte_eth_copy_dev_info Bernard Iremonger
2015-11-01 21:30     ` Thomas Monjalon
2015-11-02 10:24       ` Iremonger, Bernard
2015-10-30 15:08   ` [dpdk-dev] [PATCH v7 04/28] ixgbe: copy pci device info to eth_dev data Bernard Iremonger
2015-10-30 15:08   ` [dpdk-dev] [PATCH v7 05/28] e1000: " Bernard Iremonger
2015-10-30 15:08   ` [dpdk-dev] [PATCH v7 06/28] i40e: " Bernard Iremonger
2015-10-30 15:08   ` [dpdk-dev] [PATCH v7 07/28] fm10k: " Bernard Iremonger
2015-10-30 15:08   ` [dpdk-dev] [PATCH v7 08/28] bnx2x: " Bernard Iremonger
2015-10-30 15:08   ` [dpdk-dev] [PATCH v7 09/28] cxgbe: " Bernard Iremonger
2015-10-30 15:08   ` [dpdk-dev] [PATCH v7 10/28] enic: " Bernard Iremonger
2015-10-30 15:08   ` [dpdk-dev] [PATCH v7 11/28] mlx4: " Bernard Iremonger
2015-10-30 15:08   ` [dpdk-dev] [PATCH v7 12/28] virtio: " Bernard Iremonger
2015-10-30 15:08   ` [dpdk-dev] [PATCH v7 13/28] vmxnet3: " Bernard Iremonger
2015-10-31  8:39     ` Yong Wang
2015-10-30 15:08   ` [dpdk-dev] [PATCH v7 14/28] null: copy " Bernard Iremonger
2015-10-30 15:08   ` [dpdk-dev] [PATCH v7 15/28] ring: " Bernard Iremonger
2015-10-30 15:08   ` [dpdk-dev] [PATCH v7 16/28] pcap: " Bernard Iremonger
2015-10-30 15:08   ` [dpdk-dev] [PATCH v7 17/28] af_packet: " Bernard Iremonger
2015-10-30 15:17     ` John W. Linville
2015-10-30 15:08   ` [dpdk-dev] [PATCH v7 18/28] xenvirt: " Bernard Iremonger
2015-10-30 15:08   ` [dpdk-dev] [PATCH v7 19/28] mpipe: " Bernard Iremonger
2015-10-30 15:08   ` [dpdk-dev] [PATCH v7 20/28] bonding: " Bernard Iremonger
2015-10-30 15:08   ` [dpdk-dev] [PATCH v7 21/28] librte_ether: remove branches on pci_dev Bernard Iremonger
2015-10-30 15:08   ` [dpdk-dev] [PATCH v7 22/28] null: remove pci device Bernard Iremonger
2015-10-30 15:08   ` [dpdk-dev] [PATCH v7 23/28] ring: " Bernard Iremonger
2015-10-30 15:08   ` [dpdk-dev] [PATCH v7 24/28] pcap: " Bernard Iremonger
2015-10-30 15:08   ` [dpdk-dev] [PATCH v7 25/28] af_packet: " Bernard Iremonger
2015-10-30 15:19     ` John W. Linville
2015-10-30 15:08   ` [dpdk-dev] [PATCH v7 26/28] xenvirt: " Bernard Iremonger
2015-10-30 15:08   ` [dpdk-dev] [PATCH v7 27/28] mpipe: " Bernard Iremonger
2015-10-30 15:08   ` [dpdk-dev] [PATCH v7 28/28] bonding: " Bernard Iremonger
2015-11-01 21:35     ` Thomas Monjalon
2015-11-02 10:27       ` Iremonger, Bernard
2015-10-30 15:21   ` Thomas Monjalon [this message]
2015-10-30 15:28     ` [dpdk-dev] [PATCH v7 00/28] remove pci driver from vdevs Iremonger, Bernard
2015-11-02  5:28   ` Qiu, Michael
2015-11-02  7:35     ` Thomas Monjalon
2015-11-02 10:13       ` Iremonger, Bernard

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=1777159.x2ndGBQgqJ@xps13 \
    --to=thomas.monjalon@6wind.com \
    --cc=bernard.iremonger@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).