From: Thomas Monjalon <thomas@monjalon.net>
To: Stephen Hemminger <stephen@networkplumber.org>,
Stephen Hemminger <sthemmin@microsoft.com>
Cc: stable@dpdk.org, dev@dpdk.org
Subject: Re: [dpdk-stable] [PATCH 0/7] vmbus/netvsc: fix multi-process support
Date: Fri, 29 Mar 2019 10:51:05 +0100 [thread overview]
Message-ID: <221983826.KSRiA1B6R4@xps> (raw)
In-Reply-To: <20190208034407.7865-1-stephen@networkplumber.org>
08/02/2019 04:44, Stephen Hemminger:
> These fix the primary/secondary process model support in the
> vmbus and netvsc PMD. They do NOT fix the failsafe PMD.
>
> The last two are not bug fixes but address unnecessary
> code found while debugging the mp support.
>
> Stephen Hemminger (7):
> bus/vmbus: fix secondary process setup
> net/netvsc: fix VF support with secondary process
> bus/vmbus: fix check for mmap failure
> bus/vmbus: stop mapping if empty resource found
> bus/vmbus: map ring in secondary
> bus/vmbus: refactor secondary mapping
> net/netvsc: remove unnecessary format of ether address
Adding Cc: stable@dpdk.org for fixes.
If you do not want to backport, please check with LTS maintainers.
Applied, thanks
prev parent reply other threads:[~2019-03-29 9:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-08 3:44 Stephen Hemminger
2019-02-08 3:44 ` [dpdk-stable] [PATCH 1/7] bus/vmbus: fix secondary process setup Stephen Hemminger
2019-02-08 3:44 ` [dpdk-stable] [PATCH 2/7] net/netvsc: fix VF support with secondary process Stephen Hemminger
2019-02-08 3:44 ` [dpdk-stable] [PATCH 3/7] bus/vmbus: fix check for mmap failure Stephen Hemminger
2019-02-08 3:44 ` [dpdk-stable] [PATCH 4/7] bus/vmbus: stop mapping if empty resource found Stephen Hemminger
2019-02-08 3:44 ` [dpdk-stable] [PATCH 5/7] bus/vmbus: map ring in secondary Stephen Hemminger
2019-02-08 3:44 ` [dpdk-stable] [PATCH 6/7] bus/vmbus: refactor secondary mapping Stephen Hemminger
2019-02-08 3:44 ` [dpdk-stable] [PATCH 7/7] net/netvsc: remove unnecessary format of ether address Stephen Hemminger
2019-03-29 9:51 ` 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=221983826.KSRiA1B6R4@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).