DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Michał Krawczyk" <mk@semihalf.com>
To: David Harton <dharton@cisco.com>
Cc: Marcin Wojtas <mw@semihalf.com>,
	"Tzalik, Guy" <gtzalik@amazon.com>,
	 "Schmeilin, Evgeny" <evgenys@amazon.com>,
	dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] ena: fix init of ena pci_dev info
Date: Wed, 23 Aug 2017 07:51:07 +0200	[thread overview]
Message-ID: <CAJMMOfNDLumr4qyg-PKnH07m_805SNDtNV9bNKxpY-HSS3J1WQ@mail.gmail.com> (raw)
In-Reply-To: <20170823004145.29046-1-dharton@cisco.com>

Acked-by: Michal Krawczyk <mk@semihalf.com>

2017-08-23 2:41 GMT+02:00 David Harton <dharton@cisco.com>:

> eth_ena_dev_init() was not initializing all of the common
> pci dev info for the rte_eth_dev.  Added call to
> rte_eth_copy_pci_info() to complete the init particularly
> the driver name.
>
> Signed-off-by: David Harton <dharton@cisco.com>
> ---
>  drivers/net/ena/ena_ethdev.c | 1 +
>  1 file changed, 1 insertion(+)
>
> diff --git a/drivers/net/ena/ena_ethdev.c b/drivers/net/ena/ena_ethdev.c
> index 80ce1f3..a6c408b 100644
> --- a/drivers/net/ena/ena_ethdev.c
> +++ b/drivers/net/ena/ena_ethdev.c
> @@ -1289,6 +1289,7 @@ static int eth_ena_dev_init(struct rte_eth_dev
> *eth_dev)
>                 return 0;
>
>         pci_dev = RTE_ETH_DEV_TO_PCI(eth_dev);
> +       rte_eth_copy_pci_info(eth_dev, pci_dev);
>         adapter->pdev = pci_dev;
>
>         PMD_INIT_LOG(INFO, "Initializing %x:%x:%x.%d",
> --
> 1.8.3.1
>
>

  reply	other threads:[~2017-08-23  5:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-23  0:41 David Harton
2017-08-23  5:51 ` Michał Krawczyk [this message]
2017-08-23 10:47 ` Ferruh Yigit
2017-08-23 13:20   ` David Harton (dharton)

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=CAJMMOfNDLumr4qyg-PKnH07m_805SNDtNV9bNKxpY-HSS3J1WQ@mail.gmail.com \
    --to=mk@semihalf.com \
    --cc=dev@dpdk.org \
    --cc=dharton@cisco.com \
    --cc=evgenys@amazon.com \
    --cc=gtzalik@amazon.com \
    --cc=mw@semihalf.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).