From: "Tu, Lijuan" <lijuan.tu@intel.com>
To: "Zhou, JunX W" <junx.w.zhou@intel.com>, "dts@dpdk.org" <dts@dpdk.org>
Cc: "Zhou, JunX W" <junx.w.zhou@intel.com>
Subject: Re: [dts] [PATCH V1] hotplug/port_detach_attach_for_vhost_user_virtio_user:32 bites not support this case.
Date: Fri, 29 May 2020 08:40:09 +0000 [thread overview]
Message-ID: <8CE3E05A3F976642AAB0F4675D0AD20E0BC46A56@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <1590041419-334355-1-git-send-email-junx.w.zhou@intel.com>
Applied, thanks
> -----Original Message-----
> From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of Zhou Jun
> Sent: Thursday, May 21, 2020 2:10 PM
> To: dts@dpdk.org
> Cc: Zhou, JunX W <junx.w.zhou@intel.com>
> Subject: [dts] [PATCH V1]
> hotplug/port_detach_attach_for_vhost_user_virtio_user:32 bites not
> support this case.
>
> From: Zhou jun <junx.w.zhou@intel.com>
>
> change port_detach_attach_for_vhost_user_virtio_user's result to N/A.
>
> Signed-off-by: Zhou jun <junx.w.zhou@intel.com>
> ---
> conf/test_case_checklist.json | 16 ++++++++++++++++
> 1 file changed, 16 insertions(+)
>
> diff --git a/conf/test_case_checklist.json b/conf/test_case_checklist.json
> index 3258e46..73eda68 100644
> --- a/conf/test_case_checklist.json
> +++ b/conf/test_case_checklist.json
> @@ -3409,5 +3409,21 @@
> "Bug ID": "",
> "Comments": "NIC not support this case"
> }
> + ],
> + "port_detach_attach_for_vhost_user_virtio_user": [
> + {
> + "OS": [
> + "ALL"
> + ],
> + "NIC": [
> + "ALL"
> + ],
> + "Target": [
> + "i686-native-linuxapp-gcc",
> + "i686-native-linuxapp-icc"
> + ],
> + "Bug ID": "",
> + "Comments": "32 bites not support this case(memoory not enough)."
> + }
> ]
> }
> --
> 1.8.3.1
prev parent reply other threads:[~2020-05-29 8:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-21 6:10 Zhou Jun
2020-05-21 6:53 ` Zhou, JunX W
2020-05-29 8:40 ` Tu, Lijuan [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=8CE3E05A3F976642AAB0F4675D0AD20E0BC46A56@SHSMSX101.ccr.corp.intel.com \
--to=lijuan.tu@intel.com \
--cc=dts@dpdk.org \
--cc=junx.w.zhou@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).