From: Thomas Monjalon <thomas@monjalon.net>
To: Reshma Pattan <reshma.pattan@intel.com>
Cc: dev@dpdk.org, stable@dpdk.org, "Liang, Ma" <liang.j.ma@intel.com>,
david.hunt@intel.com
Subject: Re: [dpdk-dev] [PATCH] power: fix current frequency index
Date: Wed, 07 Oct 2020 14:55:29 +0200 [thread overview]
Message-ID: <1773292.MaKUYR1k9X@thomas> (raw)
In-Reply-To: <20200731093226.GA7166@sivswdev09.ir.intel.com>
31/07/2020 11:32, Liang, Ma:
> Hi Reshma,
>
> I'm OK with the change. That's the missing part about init process.
>
> Reviewed-by Liang Ma <liang.j.ma@intel.com>
Because of a missing colon, this review was not counted in patchwork.
I guess Dave is OK with this patch but he was not Cc'ed.
Please use --cc-cmd devtools/get-maintainer.sh when sending patches.
Dave, you can poll the backlog with this request:
https://patches.dpdk.org/project/dpdk/list/?q=power
Patch applied, thanks
prev parent reply other threads:[~2020-10-07 12:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-29 13:58 Reshma Pattan
2020-07-31 9:32 ` Liang, Ma
2020-10-07 12:55 ` Thomas Monjalon [this message]
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=1773292.MaKUYR1k9X@thomas \
--to=thomas@monjalon.net \
--cc=david.hunt@intel.com \
--cc=dev@dpdk.org \
--cc=liang.j.ma@intel.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).