From: "Hunt, David" <david.hunt@intel.com>
To: Pallantla Poornima <pallantlax.poornima@intel.com>, dev@dpdk.org
Cc: reshma.pattan@intel.com, aconole@redhat.com, ramirose@gmail.com,
stable@dpdk.org
Subject: Re: [dpdk-stable] [PATCH v3] power: fix to remove unused variable
Date: Fri, 15 Feb 2019 11:41:06 +0000 [thread overview]
Message-ID: <95365c42-195d-d3c4-b1e6-e137b16fa536@intel.com> (raw)
In-Reply-To: <1550226524-26278-1-git-send-email-pallantlax.poornima@intel.com>
On 15/2/2019 10:28 AM, Pallantla Poornima wrote:
> Variable pfi_str is removed since it is unused.
>
> Fixes: 450f0791312c ("power: add traffic pattern aware power control")
> Cc: stable@dpdk.org
>
> Signed-off-by: Pallantla Poornima <pallantlax.poornima@intel.com>
> Reviewed-by: Rami Rosen <ramirose@gmail.com>
> ---
> v3: Updated fixes line.
> v2: Removed unused variable as suggested.
> ---
> lib/librte_power/rte_power_empty_poll.c | 3 ---
> 1 file changed, 3 deletions(-)
>
> diff --git a/lib/librte_power/rte_power_empty_poll.c b/lib/librte_power/rte_power_empty_poll.c
> index e6145462f..15d4f0509 100644
> --- a/lib/librte_power/rte_power_empty_poll.c
> +++ b/lib/librte_power/rte_power_empty_poll.c
> @@ -156,11 +156,8 @@ update_training_stats(struct priority_worker *poll_stats,
> {
> RTE_SET_USED(specific_freq);
>
> - char pfi_str[32];
> uint64_t p0_empty_deq;
>
> - sprintf(pfi_str, "%02d", freq);
> -
> if (poll_stats->cur_freq == freq &&
> poll_stats->thresh[freq].trained == false) {
> if (poll_stats->thresh[freq].cur_train_iter == 0) {
Acked-by: David Hunt <david.hunt@intel.com>
next prev parent reply other threads:[~2019-02-15 11:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-15 10:28 Pallantla Poornima
2019-02-15 11:41 ` Hunt, David [this message]
2019-04-04 23:30 ` Thomas Monjalon
2019-02-15 14:14 ` Aaron Conole
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=95365c42-195d-d3c4-b1e6-e137b16fa536@intel.com \
--to=david.hunt@intel.com \
--cc=aconole@redhat.com \
--cc=dev@dpdk.org \
--cc=pallantlax.poornima@intel.com \
--cc=ramirose@gmail.com \
--cc=reshma.pattan@intel.com \
--cc=stable@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).