From: "Tu, Lijuan" <lijuan.tu@intel.com>
To: "Jiang, YuX" <yux.jiang@intel.com>, "dts@dpdk.org" <dts@dpdk.org>
Subject: RE: [dts][PATCH V1] tests/vm_hotplug: optimize script by using existed function
Date: Tue, 15 Mar 2022 03:22:23 +0000 [thread overview]
Message-ID: <b95f13f5cf96497da4040ec22d5b7738@intel.com> (raw)
In-Reply-To: <20220225180913.2691504-1-yux.jiang@intel.com>
> -----Original Message-----
> From: Jiang, YuX <yux.jiang@intel.com>
> Sent: 2022年2月26日 2:09
> To: Tu, Lijuan <lijuan.tu@intel.com>; dts@dpdk.org
> Cc: Jiang, YuX <yux.jiang@intel.com>
> Subject: [dts][PATCH V1] tests/vm_hotplug: optimize script by using existed
> function
>
> 1, use existed function wait_link_status_up to check link's status.
> 2, use new method: is_interface_up to to ensure iface's link status before
> send_packets
>
> Signed-off-by: Yu Jiang <yux.jiang@intel.com>
Applied, thanks
prev parent reply other threads:[~2022-03-15 3:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-25 18:09 Yu Jiang
2022-03-15 3:22 ` 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=b95f13f5cf96497da4040ec22d5b7738@intel.com \
--to=lijuan.tu@intel.com \
--cc=dts@dpdk.org \
--cc=yux.jiang@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).