From: Viresh Kumar <viresh.kumar@linaro.org>
To: AngeloGioacchino Del Regno <angelogioacchino.delregno@somainline.org>
Cc: Bjorn Andersson <bjorn.andersson@linaro.org>,
Ionela Voinescu <ionela.voinescu@arm.com>,
Shawn Guo <shawn.guo@linaro.org>,
"Rafael J . Wysocki" <rjw@rjwysocki.net>,
Andy Gross <agross@kernel.org>,
linux-pm@vger.kernel.org, linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH] cpufreq: qcom-hw: add missing devm_release_mem_region() call
Date: Thu, 14 Jan 2021 10:28:18 +0530 [thread overview]
Message-ID: <20210114045818.d3qu6jpekjol7ch2@vireshk-i7> (raw)
In-Reply-To: <cbd4fb28-24b8-9aa7-fe5f-24571ef6258d@somainline.org>
On 13-01-21, 23:12, AngeloGioacchino Del Regno wrote:
> Sorry, are you sure that the eventual fix shouldn't be rebased on top of my
> change (12014503) [1] that is enabling CPU scaling for all of the platforms
> that aren't getting the OSM set-up entirely by the TZ/bootloader?
> It's a pretty big series, that I've rebased 3 times already...
>
> [1]: https://patchwork.kernel.org/project/linux-arm-msm/patch/20210112182052.481888-15-angelogioacchino.delregno@somainline.org/
I am waiting for someone from Qcom background to review the stuff, perhaps Bjorn
or someone else as it is a big change.
Second, the fixes never get rebased on new stuff as they also need to make it to
stable kernels and current Linux release instead of the next one.
So, this fix will go first irrespective of the timeframe when it was posted.
Thanks Angelo.
--
viresh
next prev parent reply other threads:[~2021-01-14 4:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-12 9:52 [PATCH] cpufreq: qcom-hw: add missing devm_release_mem_region() call Shawn Guo
2021-01-12 10:14 ` Viresh Kumar
2021-01-12 11:19 ` Shawn Guo
2021-01-12 12:19 ` Ionela Voinescu
2021-01-12 14:44 ` Bjorn Andersson
2021-01-13 4:31 ` Viresh Kumar
2021-01-13 4:59 ` Bjorn Andersson
2021-01-13 5:06 ` Viresh Kumar
2021-01-13 22:12 ` AngeloGioacchino Del Regno
2021-01-14 4:58 ` Viresh Kumar [this message]
2021-01-14 5:21 ` Bjorn Andersson
2021-01-18 6:43 ` Viresh Kumar
2021-01-18 6:54 ` Shawn Guo
2021-01-18 11:03 ` Ionela Voinescu
2021-01-18 12:17 ` Shawn Guo
2021-01-19 3:36 ` Viresh Kumar
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=20210114045818.d3qu6jpekjol7ch2@vireshk-i7 \
--to=viresh.kumar@linaro.org \
--cc=agross@kernel.org \
--cc=angelogioacchino.delregno@somainline.org \
--cc=bjorn.andersson@linaro.org \
--cc=ionela.voinescu@arm.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=shawn.guo@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;
as well as URLs for NNTP newsgroup(s).