DPDK patches and discussions
 help / color / mirror / Atom feed
From: David Marchand <david.marchand@6wind.com>
To: Yong Liu <yong.liu@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] app/test-pmd: fix rte_pci_tailq not initialized before used
Date: Wed, 11 Mar 2015 18:26:31 +0100	[thread overview]
Message-ID: <CALwxeUsbpWT5EDgsTXW4yMYZzib=Rp52g4ZAiLKavvxN_LXYxA@mail.gmail.com> (raw)
In-Reply-To: <CALwxeUt59X_rj0_tXb9y4NEd6wB2UOJg5As4qF+vBmXuTEaEoQ@mail.gmail.com>

On Wed, Mar 11, 2015 at 9:59 AM, David Marchand <david.marchand@6wind.com>
wrote:

> Hello Marvin,
>
> I think this fix will break ivshmem init.
> pci_init was moved when introducing ivshmem_init.
>
> If you have a setup for this, can you check ivshmem init with your fix ?
>
> Thanks.
>

I just posted a different fix.
If yours breaks ivshmem, please test mine.

Thanks.


-- 
David Marchand

      reply	other threads:[~2015-03-11 17:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-11  8:43 Yong Liu
2015-03-11  8:59 ` David Marchand
2015-03-11 17:26   ` 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='CALwxeUsbpWT5EDgsTXW4yMYZzib=Rp52g4ZAiLKavvxN_LXYxA@mail.gmail.com' \
    --to=david.marchand@6wind.com \
    --cc=dev@dpdk.org \
    --cc=yong.liu@intel.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).