From: Bruce Richardson <bruce.richardson@intel.com>
To: Huisong Li <lihuisong@huawei.com>
Cc: <dev@dpdk.org>, <mb@smartsharesystems.com>,
<andrew.rybchenko@oktetlabs.ru>, <huangdaode@huawei.com>,
<liudongdong3@huawei.com>, <fengchengwen@huawei.com>
Subject: Re: [PATCH v2 1/2] usertools: use argparse module to get input parameter
Date: Tue, 10 Jan 2023 09:12:42 +0000 [thread overview]
Message-ID: <Y70sCvu0l9+y/I3+@bricha3-MOBL.ger.corp.intel.com> (raw)
In-Reply-To: <20230110073146.8221-2-lihuisong@huawei.com>
On Tue, Jan 10, 2023 at 03:31:45PM +0800, Huisong Li wrote:
> The telemetry client script uses argparse module to get input parameter.
> argparse uses an optional positional arguments for local socket path to
> keep backward compatibility.
>
> Signed-off-by: Huisong Li <lihuisong@huawei.com>
> ---
Acked-by: Bruce Richardson <bruce.richardson@intel.com>
next prev parent reply other threads:[~2023-01-10 9:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-09 6:55 [PATCH 0/2] usertools: use argparse module to get input and add an argment Huisong Li
2023-01-09 6:55 ` [PATCH 1/2] usertools: use argparse module to get input parameter Huisong Li
2023-01-09 9:14 ` Bruce Richardson
2023-01-09 12:26 ` lihuisong (C)
2023-01-09 14:32 ` Bruce Richardson
2023-01-10 6:24 ` lihuisong (C)
2023-01-09 6:55 ` [PATCH 2/2] usertools: add an argment for file prefix Huisong Li
2023-01-09 9:16 ` Bruce Richardson
2023-01-09 17:07 ` [PATCH] usertools: fix python warnings Stephen Hemminger
2023-02-06 7:47 ` Thomas Monjalon
2023-01-10 7:31 ` [PATCH v2 0/2] usertools: usertools: use argparse to get input and add an argument Huisong Li
2023-01-10 7:31 ` [PATCH v2 1/2] usertools: use argparse module to get input parameter Huisong Li
2023-01-10 9:12 ` Bruce Richardson [this message]
2023-01-10 7:31 ` [PATCH v2 2/2] usertools: add an argument for file prefix Huisong Li
2023-02-06 8:30 ` [PATCH v2 0/2] usertools: usertools: use argparse to get input and add an argument Thomas Monjalon
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=Y70sCvu0l9+y/I3+@bricha3-MOBL.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=dev@dpdk.org \
--cc=fengchengwen@huawei.com \
--cc=huangdaode@huawei.com \
--cc=lihuisong@huawei.com \
--cc=liudongdong3@huawei.com \
--cc=mb@smartsharesystems.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).