From: David Marchand <david.marchand@6wind.com>
To: Jan Blunck <jblunck@infradead.org>
Cc: "dev@dpdk.org" <dev@dpdk.org>, Shreyansh Jain <shreyansh.jain@nxp.com>
Subject: Re: [dpdk-dev] [PATCH 7/7] ethdev: Move filling of rte_eth_dev_info->pci_dev to dev_infos_get()
Date: Sun, 20 Nov 2016 16:23:32 +0100 [thread overview]
Message-ID: <CALwxeUvfsG+UZ1OubFTAmp7EdZ9wu7fsTG9Smp5Dbdv_5v_AsA@mail.gmail.com> (raw)
In-Reply-To: <1479636327-4166-7-git-send-email-jblunck@infradead.org>
On Sun, Nov 20, 2016 at 11:05 AM, Jan Blunck <jblunck@infradead.org> wrote:
> Only the device itself can decide its PCI or not.
>
> Signed-off-by: Jan Blunck <jblunck@infradead.org>
> ---
> drivers/net/bnx2x/bnx2x_ethdev.c | 1 +
> drivers/net/bnxt/bnxt_ethdev.c | 2 ++
> drivers/net/cxgbe/cxgbe_ethdev.c | 2 ++
> drivers/net/e1000/em_ethdev.c | 1 +
> drivers/net/e1000/igb_ethdev.c | 2 ++
> drivers/net/ena/ena_ethdev.c | 2 ++
> drivers/net/enic/enic_ethdev.c | 1 +
> drivers/net/fm10k/fm10k_ethdev.c | 1 +
> drivers/net/i40e/i40e_ethdev.c | 1 +
> drivers/net/i40e/i40e_ethdev_vf.c | 1 +
> drivers/net/ixgbe/ixgbe_ethdev.c | 2 ++
> drivers/net/mlx4/mlx4.c | 2 ++
> drivers/net/mlx5/mlx5_ethdev.c | 2 ++
> drivers/net/nfp/nfp_net.c | 1 +
> drivers/net/qede/qede_ethdev.c | 1 +
> drivers/net/szedata2/rte_eth_szedata2.c | 1 +
> drivers/net/thunderx/nicvf_ethdev.c | 2 ++
> drivers/net/virtio/virtio_ethdev.c | 1 +
> drivers/net/vmxnet3/vmxnet3_ethdev.c | 2 ++
> lib/librte_ether/rte_ethdev.c | 1 -
> 20 files changed, 28 insertions(+), 1 deletion(-)
Looks good to me.
--
David Marchand
prev parent reply other threads:[~2016-11-20 15:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-20 10:05 [dpdk-dev] [PATCH 1/7] eal: define container_of macro Jan Blunck
2016-11-20 10:05 ` [dpdk-dev] [PATCH 2/7] eal: Helper to convert to struct rte_pci_device Jan Blunck
2016-11-20 15:20 ` David Marchand
2016-11-21 16:57 ` Jan Blunck
2016-11-20 10:05 ` [dpdk-dev] [PATCH 3/7] drivers: Use ETH_DEV_PCI_DEV() helper Jan Blunck
2016-11-20 10:05 ` [dpdk-dev] [PATCH 4/7] virtio: Don't fill dev_info->driver_name Jan Blunck
2016-11-20 15:22 ` David Marchand
2016-11-21 16:34 ` Jan Blunck
2016-11-21 16:49 ` David Marchand
2016-11-21 16:52 ` Jan Blunck
2016-11-20 10:05 ` [dpdk-dev] [PATCH 5/7] virtio: Add vtpci_intr_handle() helper to get rte_intr_handle Jan Blunck
2016-11-20 10:05 ` [dpdk-dev] [PATCH 6/7] virtio: Don't depend on struct rte_eth_dev's pci_dev Jan Blunck
2016-11-20 10:05 ` [dpdk-dev] [PATCH 7/7] ethdev: Move filling of rte_eth_dev_info->pci_dev to dev_infos_get() Jan Blunck
2016-11-20 15:23 ` David Marchand [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=CALwxeUvfsG+UZ1OubFTAmp7EdZ9wu7fsTG9Smp5Dbdv_5v_AsA@mail.gmail.com \
--to=david.marchand@6wind.com \
--cc=dev@dpdk.org \
--cc=jblunck@infradead.org \
--cc=shreyansh.jain@nxp.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).