From: kgene@kernel.org (Kukjin Kim)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 5/5] Samsung driver updates for v4.3
Date: Tue, 04 Aug 2015 16:30:18 +0900 [thread overview]
Message-ID: <55C06A0A.6040407@kernel.org> (raw)
Hi,
This branch is including to support generic cpufreq driver in
mach-exynos dir. for exynos3250 and exynos5250 even the tag name is
driver. Because it is depending on clk and cpufreq changes which acked
by regarding maintainers, Mike and Viresh.
Please pull and if any problems, please kindly let me know.
Thanks,
Kukjin
The following changes since commit 995008abdf5146feb0ffdeb15ddb0e90010aff50:
Merge branch 'v4.3-next/dt-samsung-2' into
v4.3-next/clk-cpufreq-samsung (2015-08-04 15:59:14 +0900)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/kgene/linux-samsung.git
tags/samsung-driver
for you to fetch changes up to 6b1621c4a15b9110cda7cc2e2eb3e8e1a0c2bcfc:
ARM: EXYNOS: Add exynos3250 compatible to use generic cpufreq driver
(2015-08-04 15:59:33 +0900)
----------------------------------------------------------------
Samsung mach-exynos and driver updates for v4.3
- Use generic cpufreq driver for exynos3250 and exynos5250
: note depends on the following
v4.3-topic/clk-samsung (acked by clk maintainer, Mike)
v4.3-topic/cpufreq-samsung (acked by cpufreq maintainer, Viresh)
v4.3-next/dt-samsung-2 (add CPU OPP and regulator supply)
----------------------------------------------------------------
Chanwoo Choi (1):
ARM: EXYNOS: Add exynos3250 compatible to use generic cpufreq driver
Thomas Abraham (1):
ARM: EXYNOS: switch to using generic cpufreq driver for exynos5250
arch/arm/mach-exynos/exynos.c | 2 ++
1 file changed, 2 insertions(+)
next reply other threads:[~2015-08-04 7:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-04 7:30 Kukjin Kim [this message]
2015-08-13 9:18 ` [GIT PULL 5/5] Samsung driver updates for v4.3 Olof Johansson
2015-08-13 10:12 ` Kukjin Kim
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=55C06A0A.6040407@kernel.org \
--to=kgene@kernel.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;
as well as URLs for NNTP newsgroup(s).