DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Jon DeVree <nuxi@vault24.org>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] igb/e1000: Copy PCI device info after the	rte_eal_process_type() check
Date: Mon, 23 Nov 2015 22:39:49 +0100	[thread overview]
Message-ID: <5667362.LdVLoV3ZTO@xps13> (raw)
In-Reply-To: <8CEF83825BEC744B83065625E567D7C219F8A2DD@IRSMSX108.ger.corp.intel.com>

> > This fixes a bug added to these two drivers by eeefe73 (drivers: copy PCI
> > device info to ethdev data) which causes the pci info seen by the primary
> > process to become invalidated by secondary process startup.
> > This call was added after the process type check in the other drivers.
> > 
> > Signed-off-by: Jon DeVree <nuxi@vault24.org>
> 
> Acked-by: Bernard Iremonger <bernard.iremonger@intel.com>

Applied, thanks.

      reply	other threads:[~2015-11-23 21:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-23 15:13 Jon DeVree
2015-11-23 17:08 ` Iremonger, Bernard
2015-11-23 21:39   ` 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=5667362.LdVLoV3ZTO@xps13 \
    --to=thomas.monjalon@6wind.com \
    --cc=dev@dpdk.org \
    --cc=nuxi@vault24.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).