mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Zhang, Rui" <rui.zhang@intel.com>
To: "srinivas.pandruvada@linux.intel.com" 
	<srinivas.pandruvada@linux.intel.com>,
	"rafael@kernel.org" <rafael@kernel.org>,
	"daniel.lezcano@linaro.org" <daniel.lezcano@linaro.org>
Cc: "linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 0/2] intel_powerclamp: New module parameter
Date: Wed, 8 Feb 2023 07:37:04 +0000	[thread overview]
Message-ID: <15d47ea973c3ac46d68352bef2786faea9bd405d.camel@intel.com> (raw)
In-Reply-To: <20230207173219.4190013-1-srinivas.pandruvada@linux.intel.com>

On Tue, 2023-02-07 at 09:32 -0800, Srinivas Pandruvada wrote:
> Split from the series for powerclamp user of powercap idle-inject
> series:
> Use idle_inject framework for intel_powerclamp version v5.
> 
> 
> v3:
> minor document change

I have tested the V2 version of this patch series + the whole series of
Richardo's scheduler fixes from
https://lore.kernel.org/lkml/20230207045838.11243-1-ricardo.neri-calderon@linux.intel.com/

The previous scheduler problem is gone and idle injection with a
cpumask works well.

Give that we only have document change in V3,

Tested-by: Zhang Rui <rui.zhang@intel.com>

thanks,
rui

> 
> v2
> - Build warnings reported by Rui
> - Moved the powerclamp documentation to admin guide folder
> - Commit log updated as suggested by Rafael and other code suggestion
> 
> Srinivas Pandruvada (2):
>   Documentation:admin-guide: Move intel_powerclamp documentation
>   thermal/drivers/intel_powerclamp: Add two module parameters
> 
>  Documentation/admin-guide/index.rst           |   1 +
>  .../thermal/intel_powerclamp.rst              |  22 +++
>  Documentation/driver-api/thermal/index.rst    |   1 -
>  MAINTAINERS                                   |   1 +
>  drivers/thermal/intel/intel_powerclamp.c      | 177 +++++++++++++++-
> --
>  5 files changed, 180 insertions(+), 22 deletions(-)
>  rename Documentation/{driver-api => admin-
> guide}/thermal/intel_powerclamp.rst (93%)
> 

      parent reply	other threads:[~2023-02-08  7:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-07 17:32 Srinivas Pandruvada
2023-02-07 17:32 ` [PATCH v3 1/2] Documentation:admin-guide: Move intel_powerclamp documentation Srinivas Pandruvada
2023-02-07 17:32 ` [PATCH v3 2/2] thermal/drivers/intel_powerclamp: Add two module parameters Srinivas Pandruvada
2023-02-08  7:37 ` Zhang, Rui [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=15d47ea973c3ac46d68352bef2786faea9bd405d.camel@intel.com \
    --to=rui.zhang@intel.com \
    --cc=daniel.lezcano@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=rafael@kernel.org \
    --cc=srinivas.pandruvada@linux.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

all inboxes | Powered by JetHome®