From: Hajkowski <marcinx.hajkowski@intel.com>
To: david.hunt@intel.com
Cc: dev@dpdk.org, Marcin Hajkowski <marcinx.hajkowski@intel.com>
Subject: [dpdk-dev] [PATCH 0/3] rte_power enhancement
Date: Fri, 5 Apr 2019 18:22:02 +0200 [thread overview]
Message-ID: <20190405162205.4824-1-marcinx.hajkowski@intel.com> (raw)
Message-ID: <20190405162202.JMNPpor98ugrYyZ_UmQ2Pewrv4SJnjGtioumulvKirs@z> (raw)
From: Marcin Hajkowski <marcinx.hajkowski@intel.com>
Enhance rte_power API user notification by returning more
suitable value in case of power environment setting, add related tests
and some internal data cleaning corrections.
Please note that changes depends on patch
(http://patchwork.dpdk.org/patch/52349/) which should be applied
at first place.
Marcin Hajkowski (3):
power: return error in set env when power env already set
power: reset function pointers on unset env
power: add UTs for all power env types
app/test/test_power.c | 156 +++++++++++++++++++++++++++--------
lib/librte_power/rte_power.c | 24 +++++-
lib/librte_power/rte_power.h | 3 +-
3 files changed, 145 insertions(+), 38 deletions(-)
--
2.17.2
next reply other threads:[~2019-04-05 16:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-05 16:22 Hajkowski [this message]
2019-04-05 16:22 ` Hajkowski
2019-04-05 16:22 ` [dpdk-dev] [PATCH 1/3] power: return error in set env when power env already set Hajkowski
2019-04-05 16:22 ` Hajkowski
2019-04-05 16:22 ` [dpdk-dev] [PATCH 2/3] power: reset function pointers on unset env Hajkowski
2019-04-05 16:22 ` Hajkowski
2019-04-05 16:22 ` [dpdk-dev] [PATCH 3/3] power: add UTs for all power env types Hajkowski
2019-04-05 16:22 ` Hajkowski
2019-04-22 20:34 ` [dpdk-dev] [PATCH 0/3] rte_power enhancement Thomas Monjalon
2019-04-22 20:34 ` 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=20190405162205.4824-1-marcinx.hajkowski@intel.com \
--to=marcinx.hajkowski@intel.com \
--cc=david.hunt@intel.com \
--cc=dev@dpdk.org \
/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).