From: "Pattan, Reshma" <reshma.pattan@intel.com>
To: "Kearney, Tadhg" <tadhg.kearney@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "Hunt, David" <david.hunt@intel.com>,
"Burakov, Anatoly" <anatoly.burakov@intel.com>
Subject: RE: [PATCH v2 3/3] l3fwd-power: add option to call uncore API
Date: Thu, 21 Jul 2022 16:48:09 +0000 [thread overview]
Message-ID: <BYAPR11MB336663B983C6D90220CB3C06FF919@BYAPR11MB3366.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20220713140706.4143705-4-tadhg.kearney@intel.com>
> -----Original Message-----
> From: Kearney, Tadhg <tadhg.kearney@intel.com>
<snip>
> +static int
> +parse_uncore_index(const char *choice)
> +{
> + if (frequency_index > freq_array_len) {
Should this be compared against freq_array_len-1 ?. Ex: If total 10 frequencies the index can be only 0-9.
Thanks,
Reshma
next prev parent reply other threads:[~2022-07-21 16:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-13 14:07 [PATCH v2 0/3] add uncore api to be called through l3fwd-power Tadhg Kearney
2022-07-13 14:07 ` [PATCH v2 1/3] power: add uncore API to power library Tadhg Kearney
2022-07-20 16:10 ` Pattan, Reshma
2022-07-21 9:01 ` Bruce Richardson
2022-07-26 16:21 ` Kearney, Tadhg
2022-07-13 14:07 ` [PATCH v2 2/3] test/power: add unit tests for uncore API Tadhg Kearney
2022-07-13 14:07 ` [PATCH v2 3/3] l3fwd-power: add option to call " Tadhg Kearney
2022-07-21 12:15 ` Pattan, Reshma
2022-07-21 16:48 ` Pattan, Reshma [this message]
2022-09-06 10:51 ` Hunt, David
2022-09-19 9:05 ` [PATCH v3 0/3] add uncore api to be called through l3fwd-power Tadhg Kearney
2022-09-19 9:05 ` [PATCH v3 1/3] power: add uncore frequency control API to the power library Tadhg Kearney
2022-09-19 9:05 ` [PATCH v3 2/3] l3fwd-power: add option to call uncore API Tadhg Kearney
2022-09-19 9:05 ` [PATCH v3 3/3] test/power: add unit tests for " Tadhg Kearney
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=BYAPR11MB336663B983C6D90220CB3C06FF919@BYAPR11MB3366.namprd11.prod.outlook.com \
--to=reshma.pattan@intel.com \
--cc=anatoly.burakov@intel.com \
--cc=david.hunt@intel.com \
--cc=dev@dpdk.org \
--cc=tadhg.kearney@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).