From: Thomas Monjalon <thomas@monjalon.net>
To: Stephen Hemminger <sthemmin@microsoft.com>
Cc: dev@dpdk.org, Stephen Hemminger <stephen@networkplumber.org>,
stable@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v2] bus/vmbus: skip non-network devices
Date: Thu, 27 Jun 2019 23:13:55 +0200 [thread overview]
Message-ID: <3093889.Bm4lRbBU9i@xps> (raw)
In-Reply-To: <20190606003746.29399-1-stephen@networkplumber.org>
06/06/2019 02:37, Stephen Hemminger:
> From: Stephen Hemminger <sthemmin@microsoft.com>
>
> The vmbus scan code can just skip non-network devices.
> More importantly, this fixes the bug where some vmbus devices
> don't have all the attributes (like monitor_id) and a single
> failure would cause the scan to break the loop.
>
> Fixes: 831dba47bd36 ("bus/vmbus: add Hyper-V virtual bus support")
Cc: stable@dpdk.org
> Signed-off-by: Stephen Hemminger <sthemmin@microsoft.com>
Applied, thanks
prev parent reply other threads:[~2019-06-27 21:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-06 0:37 Stephen Hemminger
2019-06-27 21:13 ` 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=3093889.Bm4lRbBU9i@xps \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=stable@dpdk.org \
--cc=stephen@networkplumber.org \
--cc=sthemmin@microsoft.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).