From: code@mmayer.net (Markus Mayer)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] brcmstb-avs-cpufreq changes
Date: Wed, 18 Apr 2018 08:56:41 -0700 [thread overview]
Message-ID: <20180418155643.36464-1-code@mmayer.net> (raw)
From: Markus Mayer <mmayer@broadcom.com>
These changes are based on v4.17-rc1. The two patches are unrelated.
Patch 1/2 removes unused code that was only useful during driver
development and that has been disabled by default for a long time.
Patch 2/2 allows the driver to detect if the system supports SCMI cpufreq
Jim Quinlan (1):
cpufreq: brcmstb-avs-cpufreq: prefer SCMI cpufreq if supported
Markus Mayer (1):
cpufreq: brcmstb-avs-cpufreq: remove development debug support
drivers/cpufreq/Kconfig.arm | 10 -
drivers/cpufreq/brcmstb-avs-cpufreq.c | 339 ++--------------------------------
2 files changed, 17 insertions(+), 332 deletions(-)
--
2.7.4
next reply other threads:[~2018-04-18 15:56 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-18 15:56 Markus Mayer [this message]
2018-04-18 15:56 ` [PATCH 1/2] cpufreq: brcmstb-avs-cpufreq: remove development debug support Markus Mayer
2018-04-19 4:13 ` Viresh Kumar
2018-04-30 8:26 ` Rafael J. Wysocki
2018-04-18 15:56 ` [PATCH 2/2] cpufreq: brcmstb-avs-cpufreq: prefer SCMI cpufreq if supported Markus Mayer
2018-04-18 16:37 ` Florian Fainelli
2018-04-19 22:10 ` Markus Mayer
2018-04-19 4:16 ` Viresh Kumar
2018-04-19 10:37 ` Sudeep Holla
2018-04-20 4:42 ` Viresh Kumar
2018-04-20 9:15 ` Sudeep Holla
2018-04-20 9:35 ` Viresh Kumar
2018-04-20 16:50 ` Florian Fainelli
2018-04-23 4:23 ` Viresh Kumar
2018-04-19 10:35 ` Sudeep Holla
2018-04-19 16:21 ` Florian Fainelli
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=20180418155643.36464-1-code@mmayer.net \
--to=code@mmayer.net \
--cc=linux-arm-kernel@lists.infradead.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).