From: Sudeep Holla <sudeep.holla@arm.com>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: Sudeep Holla <sudeep.holla@arm.com>,
"Rafael J . Wysocki" <rjw@rjwysocki.net>,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 1/3] cpufreq: scpi: remove stale/outdated comment about the driver
Date: Wed, 16 Oct 2019 12:03:42 +0100 [thread overview]
Message-ID: <20191016110344.15259-2-sudeep.holla@arm.com> (raw)
In-Reply-To: <20191016110344.15259-1-sudeep.holla@arm.com>
Commit 343a8d17fa8d ("cpufreq: scpi: remove arm_big_little dependency")
removed the arm_big_little dependency from scpi driver and doesn't
provide any ops to arm_big_little cpufreq driver. Lets remove that
stale comment.
Signed-off-by: Sudeep Holla <sudeep.holla@arm.com>
---
drivers/cpufreq/scpi-cpufreq.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/drivers/cpufreq/scpi-cpufreq.c b/drivers/cpufreq/scpi-cpufreq.c
index 2b51e0718c9f..20d1f85d5f5a 100644
--- a/drivers/cpufreq/scpi-cpufreq.c
+++ b/drivers/cpufreq/scpi-cpufreq.c
@@ -1,8 +1,6 @@
/*
* System Control and Power Interface (SCPI) based CPUFreq Interface driver
*
- * It provides necessary ops to arm_big_little cpufreq driver.
- *
* Copyright (C) 2015 ARM Ltd.
* Sudeep Holla <sudeep.holla@arm.com>
*
--
2.17.1
next prev parent reply other threads:[~2019-10-16 11:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-16 11:03 [PATCH 0/3] cpufreq: merge arm_big_little and vexpress-spc Sudeep Holla
2019-10-16 11:03 ` Sudeep Holla [this message]
2019-10-16 11:03 ` [PATCH 2/3] " Sudeep Holla
2019-10-17 2:39 ` Viresh Kumar
2019-10-17 9:26 ` Sudeep Holla
2019-10-17 9:30 ` Viresh Kumar
2019-10-17 9:58 ` Sudeep Holla
2019-10-16 11:03 ` [PATCH 3/3] cpufreq: simplify and remove lots of debug messages Sudeep Holla
2019-10-17 2:42 ` Viresh Kumar
2019-10-17 9:14 ` Sudeep Holla
2019-10-17 2:43 ` [PATCH 0/3] cpufreq: merge arm_big_little and vexpress-spc 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=20191016110344.15259-2-sudeep.holla@arm.com \
--to=sudeep.holla@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--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;
as well as URLs for NNTP newsgroup(s).