From: viresh.kumar@linaro.org (Viresh Kumar)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 3/7] cpufreq: sort the drivers in ARM part
Date: Tue, 12 Dec 2017 12:27:12 +0530 [thread overview]
Message-ID: <20171212065712.GH25177@vireshk-i7> (raw)
In-Reply-To: <20171207135616.23670-4-gregory.clement@free-electrons.com>
On 07-12-17, 14:56, Gregory CLEMENT wrote:
> Keep the driver files alphabetically sorted.
>
> Signed-off-by: Gregory CLEMENT <gregory.clement@free-electrons.com>
> ---
> drivers/cpufreq/Makefile | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
Acked-by: Viresh Kumar <viresh.kumar@linaro.org>
--
viresh
next prev parent reply other threads:[~2017-12-12 6:57 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-07 13:56 [PATCH v2 0/7] Add CPU Frequency scaling support on Armada 37xx Gregory CLEMENT
2017-12-07 13:56 ` [PATCH v2 1/7] dt-bindings: marvell: Add documentation for the North Bridge PM " Gregory CLEMENT
2017-12-07 23:36 ` Rob Herring
2017-12-07 13:56 ` [PATCH v2 2/7] cpufreq: ARM: sort the Kconfig menu Gregory CLEMENT
2017-12-12 6:56 ` Viresh Kumar
2017-12-07 13:56 ` [PATCH v2 3/7] cpufreq: sort the drivers in ARM part Gregory CLEMENT
2017-12-12 6:57 ` Viresh Kumar [this message]
2017-12-07 13:56 ` [PATCH v2 4/7] cpufreq: mvebu: Use dev_pm_opp_remove() Gregory CLEMENT
2017-12-12 7:21 ` Viresh Kumar
2017-12-12 7:28 ` Thomas Petazzoni
2017-12-12 7:33 ` Viresh Kumar
2017-12-07 13:56 ` [PATCH v2 5/7] MAINTAINERS: add new entries for Armada 37xx cpufreq driver Gregory CLEMENT
2017-12-12 7:22 ` Viresh Kumar
2017-12-07 13:56 ` [PATCH v2 6/7] cpufreq: Add DVFS support for Armada 37xx Gregory CLEMENT
2017-12-12 7:24 ` Viresh Kumar
2017-12-13 16:45 ` Gregory CLEMENT
2017-12-07 13:56 ` [PATCH v2 7/7] arm64: dts: marvell: armada-37xx: add nodes allowing cpufreq support Gregory CLEMENT
2017-12-07 17:14 ` [PATCH v2 0/7] Add CPU Frequency scaling support on Armada 37xx Rafael J. Wysocki
2017-12-07 17:58 ` Gregory CLEMENT
2017-12-07 21:19 ` Rafael J. Wysocki
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=20171212065712.GH25177@vireshk-i7 \
--to=viresh.kumar@linaro.org \
--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