From: "Zhang, YanX A" <yanx.a.zhang@intel.com>
To: "Ma, LihongX" <lihongx.ma@intel.com>, "dts@dpdk.org" <dts@dpdk.org>
Cc: "Ma, LihongX" <lihongx.ma@intel.com>
Subject: Re: [dts] [patch V1] alter the regular expression format of hostfwd value
Date: Mon, 13 May 2019 07:58:02 +0000 [thread overview]
Message-ID: <2C49E4B25FAD1D419F7564D633EF72E1583657@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <4DC48DF9BDA3E54A836D2D3C057DEC6F0B17EF21@SHSMSX101.ccr.corp.intel.com>
tested-by: Zhang, YanX A <yanx.a.zhang@intel.com>
> -----Original Message-----
> From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of lihong
> Sent: Monday, May 13, 2019 8:29 AM
> To: dts@dpdk.org
> Cc: Ma, LihongX <lihongx.ma@intel.com>
> Subject: [dts] [patch V1] alter the regular expression format of hostfwd value
>
> Signed-off-by: lihong <lihongx.ma@intel.com>
> ---
> framework/qemu_kvm.py | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/framework/qemu_kvm.py b/framework/qemu_kvm.py index
> c3e8f37..80a39c8 100644
> --- a/framework/qemu_kvm.py
> +++ b/framework/qemu_kvm.py
> @@ -562,7 +562,7 @@ class QEMUKvm(VirtBase):
> Use regular expression to check if hostfwd value format is correct.
> """
> regx_ip = '\d{1,3}\.\d{1,3}\.\d{1,3}\.\d{1,3}'
> - regx_hostfwd = r'["tcp" | "udp"]?:%s?:\d+-%s?:\d+' % (regx_ip,
> regx_ip)
> + regx_hostfwd = r'(tcp|udp)?:(%s)?:\d+-(%s)?:\d+' % (regx_ip,
> + regx_ip)
> if not re.match(regx_hostfwd, opt_hostfwd):
> raise Exception("Option opt_hostfwd format is not correct,\n"
> +
> "it is %s,\n " % opt_hostfwd +
> --
> 2.7.4
next prev parent reply other threads:[~2019-05-13 7:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-13 0:29 lihong
[not found] ` <4DC48DF9BDA3E54A836D2D3C057DEC6F0B17EF21@SHSMSX101.ccr.corp.intel.com>
2019-05-13 7:58 ` Zhang, YanX A [this message]
2019-05-22 8:58 ` Tu, Lijuan
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=2C49E4B25FAD1D419F7564D633EF72E1583657@shsmsx102.ccr.corp.intel.com \
--to=yanx.a.zhang@intel.com \
--cc=dts@dpdk.org \
--cc=lihongx.ma@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).