From: Thomas Monjalon <thomas@monjalon.net>
To: Qi Zhang <qi.z.zhang@intel.com>
Cc: dev@dpdk.org, gaetan.rivet@6wind.com, stable@dpdk.org
Subject: Re: [dpdk-stable] [dpdk-dev] [PATCH] bus/vdev: fix device argument corrupt after bus scan
Date: Sun, 28 Oct 2018 18:32:17 +0100 [thread overview]
Message-ID: <12331205.kF6hlE4all@xps> (raw)
In-Reply-To: <20181025033036.23680-1-qi.z.zhang@intel.com>
25/10/2018 05:30, Qi Zhang:
> It's not necessary to insert device argment to devargs_list
> during bus scan, but this happens when we try to attach a
> device on secondary process. The patch fix the issue.
>
> Fixes: cdb068f031c6 ("bus/vdev: scan by multi-process channel")
> Cc: stable@dpdk.org
>
> Signed-off-by: Qi Zhang <qi.z.zhang@intel.com>
Applied, thanks
prev parent reply other threads:[~2018-10-28 17:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-25 3:30 [dpdk-stable] " Qi Zhang
2018-10-25 9:51 ` Gaëtan Rivet
2018-10-25 14:56 ` Zhang, Qi Z
2018-10-25 15:03 ` Gaëtan Rivet
2018-10-25 15:18 ` Zhang, Qi Z
2018-10-25 15:26 ` Gaëtan Rivet
2018-10-28 17:32 ` 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=12331205.kF6hlE4all@xps \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=gaetan.rivet@6wind.com \
--cc=qi.z.zhang@intel.com \
--cc=stable@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).