From: David Marchand <david.marchand@redhat.com>
To: Sivaprasad Tummala <sivaprasad.tummala@amd.com>
Cc: david.hunt@intel.com, anatoly.burakov@intel.com,
ferruh.yigit@amd.com, dev@dpdk.org,
Thomas Monjalon <thomas@monjalon.net>,
"Mcnamara, John" <john.mcnamara@intel.com>
Subject: Re: [PATCH v2 1/2] power: refactor uncore power management interfaces
Date: Tue, 17 Oct 2023 10:19:07 +0200 [thread overview]
Message-ID: <CAJFAV8wnkj1suwDXAg4_bQ9k99LEfxROtx5ouphRM6qBNs76jA@mail.gmail.com> (raw)
In-Reply-To: <20230816100958.1022206-1-sivaprasad.tummala@amd.com>
On Wed, Aug 16, 2023 at 12:10 PM Sivaprasad Tummala
<sivaprasad.tummala@amd.com> wrote:
>
> currently the uncore power management implementation is vendor specific.
> Added new vendor agnostic uncore power interface similar to rte_power
> and rename specific implementations ("rte_power_intel_uncore") to
> "power_intel_uncore" along with functions.
>
> Signed-off-by: Sivaprasad Tummala <sivaprasad.tummala@amd.com>
No news from the maintainers is not a good news...
But, given Anatoly was not against it, I took this series for rc1.
Applied with some fixes on doc and style, and added an entry in the RN, thanks.
--
David Marchand
prev parent reply other threads:[~2023-10-17 8:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-03 17:03 [RFC PATCH] " Sivaprasad Tummala
2023-05-17 11:42 ` Tummala, Sivaprasad
2023-05-19 9:42 ` Burakov, Anatoly
2023-08-11 10:25 ` [PATCH v1 1/2] " Sivaprasad Tummala
2023-08-11 10:25 ` [PATCH v1 2/2] power: refactor uncore power management implementation Sivaprasad Tummala
2023-08-16 10:09 ` [PATCH v2 1/2] power: refactor uncore power management interfaces Sivaprasad Tummala
2023-08-16 10:09 ` [PATCH v2 2/2] power: refactor uncore power management implementation Sivaprasad Tummala
2023-10-06 9:03 ` [PATCH v2 1/2] power: refactor uncore power management interfaces David Marchand
2023-10-09 13:56 ` Tummala, Sivaprasad
2023-10-17 8:19 ` David Marchand [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=CAJFAV8wnkj1suwDXAg4_bQ9k99LEfxROtx5ouphRM6qBNs76jA@mail.gmail.com \
--to=david.marchand@redhat.com \
--cc=anatoly.burakov@intel.com \
--cc=david.hunt@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@amd.com \
--cc=john.mcnamara@intel.com \
--cc=sivaprasad.tummala@amd.com \
--cc=thomas@monjalon.net \
/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).