From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: "Qiu, Michael" <michael.qiu@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v6] VFIO: Avoid to enable vfio while the module not loaded
Date: Fri, 19 Dec 2014 09:23:34 +0100 [thread overview]
Message-ID: <4162168.RCAhVMLdi5@xps13> (raw)
In-Reply-To: <533710CFB86FA344BFBF2D6802E60286CA1227@SHSMSX101.ccr.corp.intel.com>
2014-12-19 07:09, Qiu, Michael:
> Hi Thomas,
>
> Will you plan to merge this patch? If yes, you plan to merge it into
> 1.8 or 2.0?
It won't be in 1.8 for 2 reasons:
- there is a risk to break something in some environments, so need more tests
- you add a function protoype in eal common without bsd implementation
--
Thomas
next prev parent reply other threads:[~2014-12-19 8:24 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-04 3:36 [dpdk-dev] [PATCH] " Michael Qiu
2014-12-04 10:00 ` [dpdk-dev] [PATCH v2] " Michael Qiu
2014-12-05 10:00 ` Burakov, Anatoly
2014-12-08 7:25 ` Qiu, Michael
2014-12-08 18:47 ` Burakov, Anatoly
2014-12-09 2:47 ` Qiu, Michael
2014-12-09 9:51 ` Burakov, Anatoly
2014-12-08 8:27 ` [dpdk-dev] [PATCH v3] " Michael Qiu
2014-12-08 9:54 ` Burakov, Anatoly
2014-12-08 10:28 ` Qiu, Michael
2014-12-08 10:44 ` [dpdk-dev] [PATCH v4] " Michael Qiu
2014-12-08 12:19 ` Burakov, Anatoly
2014-12-08 15:28 ` Qiu, Michael
2014-12-10 0:17 ` Xie, Huawei
2014-12-10 2:06 ` Qiu, Michael
2014-12-10 2:22 ` [dpdk-dev] [PATCH v5] " Michael Qiu
2014-12-10 9:21 ` Burakov, Anatoly
2014-12-10 11:29 ` Qiu, Michael
2014-12-10 11:46 ` [dpdk-dev] [PATCH v6] " Michael Qiu
2014-12-10 11:48 ` Burakov, Anatoly
2014-12-19 7:09 ` Qiu, Michael
2014-12-19 8:23 ` Thomas Monjalon [this message]
2014-12-22 1:21 ` Qiu, Michael
2015-01-15 13:38 ` Thomas Monjalon
2015-01-15 13:42 ` Burakov, Anatoly
2015-01-15 13:51 ` Thomas Monjalon
2014-12-04 13:12 ` [dpdk-dev] [PATCH] " Burakov, Anatoly
2014-12-04 13:47 ` Qiu, Michael
2014-12-04 16:31 ` Burakov, Anatoly
2014-12-05 4:01 ` Qiu, Michael
2014-12-04 13:13 ` Burakov, Anatoly
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=4162168.RCAhVMLdi5@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=michael.qiu@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).