From: Will Deacon <will@kernel.org>
To: Viresh Kumar <viresh.kumar@linaro.org>,
Catalin Marinas <catalin.marinas@arm.com>
Cc: kernel-team@android.com, Will Deacon <will@kernel.org>,
Ionela Voinescu <ionela.voinescu@arm.com>,
linux-kernel@vger.kernel.org,
Vincent Guittot <vincent.guittot@linaro.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH V4 0/3] arm64: topology: improvements
Date: Wed, 20 Jan 2021 13:01:08 +0000 [thread overview]
Message-ID: <161114698073.222302.6333959432282953596.b4-ty@kernel.org> (raw)
In-Reply-To: <cover.1610104461.git.viresh.kumar@linaro.org>
On Fri, 8 Jan 2021 16:46:50 +0530, Viresh Kumar wrote:
> Here is the V4 with the general improvements for topology stuff. This
> cleans up the code and makes it work with cpufreq modules.
>
> V4:
> - Added Rby from Ionela.
> - In 3/3, Print cpus instead of amu_fie_cpus and make it pr_debug
> instead.
>
> [...]
Applied to arm64 (for-next/topology), thanks!
[1/3] arm64: topology: Avoid the have_policy check
https://git.kernel.org/arm64/c/384e5699e101
[2/3] arm64: topology: Reorder init_amu_fie() a bit
https://git.kernel.org/arm64/c/47b10b737c07
[3/3] arm64: topology: Make AMUs work with modular cpufreq drivers
https://git.kernel.org/arm64/c/a5f1b187cd24
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
prev parent reply other threads:[~2021-01-20 14:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-08 11:16 Viresh Kumar
2021-01-08 11:16 ` [PATCH V4 1/3] arm64: topology: Avoid the have_policy check Viresh Kumar
2021-01-08 11:16 ` [PATCH V4 2/3] arm64: topology: Reorder init_amu_fie() a bit Viresh Kumar
2021-01-08 11:16 ` [PATCH V4 3/3] arm64: topology: Make AMUs work with modular cpufreq drivers Viresh Kumar
2021-01-08 15:51 ` Ionela Voinescu
2021-01-08 15:53 ` [PATCH V4 0/3] arm64: topology: improvements Ionela Voinescu
2021-01-11 4:46 ` Viresh Kumar
2021-01-19 9:12 ` Viresh Kumar
2021-01-20 13:01 ` Will Deacon [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=161114698073.222302.6333959432282953596.b4-ty@kernel.org \
--to=will@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=ionela.voinescu@arm.com \
--cc=kernel-team@android.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vincent.guittot@linaro.org \
--cc=viresh.kumar@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
all inboxes | Powered by JetHome®