From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Niklas Cassel <nks@flawful.org>
Cc: linux-pm@vger.kernel.org, linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH 0/5] qcom-cpr fixes for rjw bleeding-edge
Date: Sun, 29 Dec 2019 23:45:46 +0100 [thread overview]
Message-ID: <3833311.45NX9LJ36M@kreacher> (raw)
In-Reply-To: <20191223141934.19837-1-nks@flawful.org>
On Monday, December 23, 2019 3:19:29 PM CET Niklas Cassel wrote:
> Hello Rafael,
>
> Here comes some bug fixes for qcom-cpr that were detected
> once the driver got some more build testing.
>
> Patches 1-2 fix warnings detected by the intel test robot.
>
> Patch 3 fixes an error I detected when doing an allnoconfig
> and enabling simply the qcom-cpr driver.
>
> Patches 4-5 are only detected when building with W=1.
> However, I decided to fix these as well, in order to hopefully
> avoid any further build test reports.
>
> The series is based on your bleeding-edge branch.
> Feel free to squash them with the existing commit if you
> so desire.
>
> Niklas Cassel (5):
> power: avs: qcom-cpr: fix invalid printk specifier in debug print
> power: avs: qcom-cpr: fix unsigned expression compared with zero
> power: avs: qcom-cpr: make sure that regmap is available
> power: avs: qcom-cpr: remove set but unused variable
> power: avs: qcom-cpr: make cpr_get_opp_hz_for_req() static
>
> drivers/power/avs/Kconfig | 1 +
> drivers/power/avs/qcom-cpr.c | 18 ++++++++++--------
> 2 files changed, 11 insertions(+), 8 deletions(-)
>
>
All patches in the series applied as 5.6 material, thanks!
prev parent reply other threads:[~2019-12-29 22:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-23 14:19 [PATCH 0/5] qcom-cpr fixes for rjw bleeding-edge Niklas Cassel
2019-12-23 14:19 ` [PATCH 1/5] power: avs: qcom-cpr: fix invalid printk specifier in debug print Niklas Cassel
2019-12-27 6:45 ` Bjorn Andersson
2019-12-23 14:19 ` [PATCH 2/5] power: avs: qcom-cpr: fix unsigned expression compared with zero Niklas Cassel
2019-12-27 6:47 ` Bjorn Andersson
2019-12-23 14:19 ` [PATCH 3/5] power: avs: qcom-cpr: make sure that regmap is available Niklas Cassel
2019-12-27 6:51 ` Bjorn Andersson
2019-12-23 14:19 ` [PATCH 4/5] power: avs: qcom-cpr: remove set but unused variable Niklas Cassel
2019-12-27 6:52 ` Bjorn Andersson
2019-12-23 14:19 ` [PATCH 5/5] power: avs: qcom-cpr: make cpr_get_opp_hz_for_req() static Niklas Cassel
2019-12-27 6:56 ` Bjorn Andersson
2019-12-29 22:45 ` Rafael J. Wysocki [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=3833311.45NX9LJ36M@kreacher \
--to=rjw@rjwysocki.net \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=nks@flawful.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).