From: Richael Zhuang <richael.zhuang@arm.com>
To: dev@dpdk.org
Cc: zhiminx.huang@intel.com
Subject: [dpdk-dev] [PATCH v1 0/1] test/power: check cpuinfo cur freq before
Date: Wed, 14 Jul 2021 16:44:06 +0800 [thread overview]
Message-ID: <20210714084407.51979-1-richael.zhuang@arm.com> (raw)
v1:
fix CPU frequency check
Richael Zhuang (1):
test/power: check cpuinfo cur freq before scaling cur freq
app/test/test_power_cpufreq.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
--
2.20.1
next reply other threads:[~2021-07-14 8:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-14 8:44 Richael Zhuang [this message]
2021-07-14 8:44 ` [dpdk-dev] [PATCH v1 1/1] test/power: check cpuinfo cur freq before scaling cur freq Richael Zhuang
2021-07-14 9:15 ` David Hunt
2021-07-14 9:23 ` Richael Zhuang
2021-07-14 10:13 ` David Hunt
2021-07-14 10:29 ` Richael Zhuang
2021-07-14 10:44 ` [dpdk-dev] [PATCH v2 0/1] test/power: fix CPU frequency check Richael Zhuang
2021-07-14 10:44 ` [dpdk-dev] [PATCH v2 1/1] " Richael Zhuang
2021-07-14 12:23 ` David Hunt
2021-07-15 1:44 ` Richael Zhuang
2021-07-20 15:20 ` David Marchand
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=20210714084407.51979-1-richael.zhuang@arm.com \
--to=richael.zhuang@arm.com \
--cc=dev@dpdk.org \
--cc=zhiminx.huang@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).