From: Viresh Kumar <viresh.kumar@linaro.org>
To: Vladimir Zapolskiy <vladimir.zapolskiy@linaro.org>
Cc: "Rafael J. Wysocki" <rafael@kernel.org>,
Thara Gopinath <thara.gopinath@linaro.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
linux-arm-msm@vger.kernel.org, linux-pm@vger.kernel.org
Subject: Re: [PATCH 0/3] cpufreq: qcom-hw: a few fixes in qcom cpufreq driver
Date: Thu, 25 Nov 2021 12:20:14 +0530 [thread overview]
Message-ID: <20211125065014.phkfugo2wptosrgv@vireshk-i7> (raw)
In-Reply-To: <20211111154808.2024808-1-vladimir.zapolskiy@linaro.org>
On 11-11-21, 17:48, Vladimir Zapolskiy wrote:
> I find it essential to resend a fix from Ard and also add two more
> lesser fixes to the set, review and comments are more than welcome.
>
> Ard Biesheuvel (1):
> cpufreq: qcom-cpufreq-hw: Avoid stack buffer for IRQ name
>
> Vladimir Zapolskiy (2):
> cpufreq: qcom-hw: Fix probable nested interrupt handling
> cpufreq: qcom-hw: Set CPU affinity of dcvsh interrupts
>
> drivers/cpufreq/qcom-cpufreq-hw.c | 17 +++++++++++------
> 1 file changed, 11 insertions(+), 6 deletions(-)
Applied. Thanks.
--
viresh
prev parent reply other threads:[~2021-11-25 6:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-11 15:48 [PATCH 0/3] cpufreq: qcom-hw: a few fixes in qcom cpufreq driver Vladimir Zapolskiy
2021-11-11 15:48 ` [PATCH 1/3][RESEND] cpufreq: qcom-cpufreq-hw: Avoid stack buffer for IRQ name Vladimir Zapolskiy
2021-11-11 16:36 ` Matthias Kaehlcke
2021-11-12 20:16 ` Dmitry Baryshkov
2021-11-13 18:55 ` Bjorn Andersson
2021-11-13 18:53 ` Bjorn Andersson
2021-11-11 15:48 ` [PATCH 2/3] cpufreq: qcom-hw: Fix probable nested interrupt handling Vladimir Zapolskiy
2021-11-11 16:28 ` Matthias Kaehlcke
2021-11-13 18:52 ` Bjorn Andersson
2021-11-11 15:48 ` [PATCH 3/3] cpufreq: qcom-hw: Set CPU affinity of dcvsh interrupts Vladimir Zapolskiy
2021-11-11 16:32 ` Matthias Kaehlcke
2021-11-25 6:50 ` Viresh Kumar [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=20211125065014.phkfugo2wptosrgv@vireshk-i7 \
--to=viresh.kumar@linaro.org \
--cc=bjorn.andersson@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=thara.gopinath@linaro.org \
--cc=vladimir.zapolskiy@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.