From: Viresh Kumar <viresh.kumar@linaro.org>
To: Pierre Gondois <pierre.gondois@arm.com>
Cc: linux-kernel@vger.kernel.org, Ionela.Voinescu@arm.com,
Dietmar.Eggemann@arm.com, "Rafael J. Wysocki" <rafael@kernel.org>,
Andy Gross <agross@kernel.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
Vladimir Zapolskiy <vladimir.zapolskiy@linaro.org>,
linux-pm@vger.kernel.org, linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH 0/4] cpufreq: qcom-hw: LMH irq/hotplug interractions
Date: Mon, 4 Jul 2022 15:28:56 +0530 [thread overview]
Message-ID: <20220704095856.s3abmelpd2744nyl@vireshk-i7> (raw)
In-Reply-To: <a9ab7982-b235-ef5f-2c1b-ecbc421552d1@arm.com>
On 04-07-22, 11:55, Pierre Gondois wrote:
> Hello,
> I saw that:
> https://lore.kernel.org/all/20220617064421.l4vshytmqtittzee@vireshk-i7/
>
> was applied, so this patch-set would need to be rebased. Please let me
> know if you think it requires modifications before it gets rebased,
Everything else looks fine, just rebase and resend. Thanks.
--
viresh
prev parent reply other threads:[~2022-07-04 9:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-15 14:43 [PATCH 0/4] cpufreq: qcom-hw: LMH irq/hotplug interractions Pierre Gondois
2022-06-15 14:43 ` [PATCH 1/4] cpufreq: qcom-hw: Reset cancel_throttle when policy is re-enabled Pierre Gondois
2022-06-15 14:43 ` [PATCH 2/4] cpufreq: qcom-hw: Disable LMH irq when disabling policy Pierre Gondois
2022-06-15 14:43 ` [PATCH 3/4] cpufreq: qcom-hw: Remove deprecated irq_set_affinity_hint() call Pierre Gondois
2022-06-15 14:43 ` [PATCH 4/4] cpufreq: Change order of online() CB and policy->cpus modification Pierre Gondois
2022-06-16 6:17 ` Viresh Kumar
2022-07-04 9:55 ` [PATCH 0/4] cpufreq: qcom-hw: LMH irq/hotplug interractions Pierre Gondois
2022-07-04 9:58 ` 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=20220704095856.s3abmelpd2744nyl@vireshk-i7 \
--to=viresh.kumar@linaro.org \
--cc=Dietmar.Eggemann@arm.com \
--cc=Ionela.Voinescu@arm.com \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=pierre.gondois@arm.com \
--cc=rafael@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox