From: "Dong, JunX" <junx.dong@intel.com>
To: "Juraj Linkeš" <juraj.linkes@pantheon.tech>,
"dts@dpdk.org" <dts@dpdk.org>
Cc: "Tu, Lijuan" <lijuan.tu@intel.com>,
"ohilyard@iol.unh.edu" <ohilyard@iol.unh.edu>
Subject: RE: [PATCH v1 1/2] stats_reporter: properly use iterable in for cycle
Date: Thu, 28 Apr 2022 03:15:17 +0000 [thread overview]
Message-ID: <BN6PR11MB1393CE9FB7C8184701CEF751EAFD9@BN6PR11MB1393.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20220427074152.4144881-1-juraj.linkes@pantheon.tech>
Acked-by: Jun Dong <junx.dong@intel.com>
> -----Original Message-----
> From: Juraj Linkeš <juraj.linkes@pantheon.tech>
> Sent: Wednesday, April 27, 2022 3:42 PM
> To: Dong, JunX <junx.dong@intel.com>; Tu, Lijuan <lijuan.tu@intel.com>;
> ohilyard@iol.unh.edu
> Cc: dts@dpdk.org; Juraj Linkeš <juraj.linkes@pantheon.tech>
> Subject: [PATCH v1 1/2] stats_reporter: properly use iterable in for cycle
>
> Signed-off-by: Juraj Linkeš <juraj.linkes@pantheon.tech>
> ---
> framework/stats_reporter.py | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/framework/stats_reporter.py b/framework/stats_reporter.py
> index 80ac942c..1c1ab3fd 100644
> --- a/framework/stats_reporter.py
> +++ b/framework/stats_reporter.py
> @@ -70,7 +70,7 @@ class StatsReporter(object):
> "dpdk_version =
> {}\n".format(self.result.current_dpdk_version(duts[0]))
> )
> else:
> - for dut in duts():
> + for dut in duts:
> dpdk_version = self.result.current_dpdk_version(dut)
> self.stats_file.write(
> "{}.dpdk_version = {}\n".format(dut, dpdk_version)
> --
> 2.20.1
next prev parent reply other threads:[~2022-04-28 3:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-27 7:41 Juraj Linkeš
2022-04-27 7:41 ` [PATCH v1 2/2] python: fix shebangs Juraj Linkeš
2022-04-28 3:15 ` Dong, JunX [this message]
2022-05-05 6:47 [PATCH v1 1/2] stats_reporter: properly use iterable in for cycle lijuan.tu
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=BN6PR11MB1393CE9FB7C8184701CEF751EAFD9@BN6PR11MB1393.namprd11.prod.outlook.com \
--to=junx.dong@intel.com \
--cc=dts@dpdk.org \
--cc=juraj.linkes@pantheon.tech \
--cc=lijuan.tu@intel.com \
--cc=ohilyard@iol.unh.edu \
/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).