From: Krzysztof Kozlowski <krzk@kernel.org>
To: "Paweł Chmiel" <pawel.mikolaj.chmiel@gmail.com>
Cc: mark.rutland@arm.com, devicetree@vger.kernel.org,
linux-samsung-soc@vger.kernel.org, linux-pm@vger.kernel.org,
viresh.kumar@linaro.org, rjw@rjwysocki.net,
linux@armlinux.org.uk, robh+dt@kernel.org,
linux-kernel@vger.kernel.org, kgene@kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 4/4] ARM: defconfig: s5pv210: Add cpufreq support
Date: Sun, 13 Jan 2019 10:34:16 +0100 [thread overview]
Message-ID: <20190113093416.GA27934@kozik-lap> (raw)
In-Reply-To: <20190110205215.22030-5-pawel.mikolaj.chmiel@gmail.com>
On Thu, Jan 10, 2019 at 09:52:15PM +0100, Paweł Chmiel wrote:
> This commit enables cpufreq support for all s5pv210 devices.
>
> Signed-off-by: Paweł Chmiel <pawel.mikolaj.chmiel@gmail.com>
> ---
> arch/arm/configs/s5pv210_defconfig | 6 ++++++
Thanks, applied.
Best regards,
Krzysztof
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2019-01-13 9:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-10 20:52 [PATCH v2 0/4] ARM: dts: s5pv210: Enable cpufreq support Paweł Chmiel
2019-01-10 20:52 ` [PATCH v2 1/4] ARM: dts: s5pv210: Add dmc nodes Paweł Chmiel
2019-01-11 8:32 ` Krzysztof Kozlowski
2019-01-11 9:41 ` Viresh Kumar
2019-01-11 9:47 ` Krzysztof Kozlowski
2019-01-10 20:52 ` [PATCH v2 2/4] cpufreq: s5pv210: Don't flood kernel log after cpufreq change Paweł Chmiel
2019-01-10 20:52 ` [PATCH v2 3/4] cpufreq: s5pv210: Defer probe if getting regulators fail Paweł Chmiel
2019-01-11 9:46 ` Krzysztof Kozlowski
2019-01-11 9:53 ` Paweł Chmiel
2019-01-10 20:52 ` [PATCH v2 4/4] ARM: defconfig: s5pv210: Add cpufreq support Paweł Chmiel
2019-01-13 9:34 ` Krzysztof Kozlowski [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=20190113093416.GA27934@kozik-lap \
--to=krzk@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kgene@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mark.rutland@arm.com \
--cc=pawel.mikolaj.chmiel@gmail.com \
--cc=rjw@rjwysocki.net \
--cc=robh+dt@kernel.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;
as well as URLs for NNTP newsgroup(s).