From: "Burakov, Anatoly" <anatoly.burakov@intel.com>
To: David Hunt <david.hunt@intel.com>, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v1] examples/power: fix policy handling for fifo
Date: Tue, 16 Jul 2019 14:44:07 +0100 [thread overview]
Message-ID: <33be55b0-d1ed-5564-873c-25bcbb51eec4@intel.com> (raw)
In-Reply-To: <20190716111112.32427-1-david.hunt@intel.com>
On 16-Jul-19 12:11 PM, David Hunt wrote:
> While the core frequency scale-up and scale down all works fine with the
> fifo-per-core functionaliry, there was a gap for policy handling. When
> creating or destroying a policy, the core associated with the fifo
> needs to be automatically added to the core list, so the policy is
> associated with the correct core.
>
> Fixes: 221e7026d521 ("examples/power: add FIFO per core for JSON interface")
>
> Signed-off-by: David Hunt <david.hunt@intel.com>
> ---
LGTM
Acked-by: Anatoly Burakov <anatoly.burakov@intel.com>
--
Thanks,
Anatoly
next prev parent reply other threads:[~2019-07-16 13:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-16 11:11 David Hunt
2019-07-16 13:44 ` Burakov, Anatoly [this message]
2019-07-17 20:52 ` 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=33be55b0-d1ed-5564-873c-25bcbb51eec4@intel.com \
--to=anatoly.burakov@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).