From: Olof Johansson <olof@lixom.net>
To: Kukjin Kim <kgene.kim@samsung.com>
Cc: arm@kernel.org, 'Arnd Bergmann' <arnd@arndb.de>,
'Kevin Hilman' <khilman@linaro.org>,
linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org,
'Tomasz Figa' <t.figa@samsung.com>
Subject: Re: [GIT PULL 2/5] Samsung clock updates for 3.16
Date: Thu, 29 May 2014 11:17:08 -0700 [thread overview]
Message-ID: <20140529181708.GA18481@quad.lixom.net> (raw)
In-Reply-To: <014501cf73c8$5eb66960$1c233c20$@samsung.com>
On Tue, May 20, 2014 at 10:11:03AM +0900, Kukjin Kim wrote:
> The following changes since commit 34c453ce16633539a94a2e876faeb731ac1be899:
>
> ARM: S3C24XX: fix merge conflict (2014-05-15 05:54:38 +0900)
>
> are available in the git repository at:
>
> http://git.kernel.org/pub/scm/linux/kernel/git/kgene/linux-samsung.git
> tags/samsung-clk
>
> for you to fetch changes up to 6520e968eef4f88c076a84a80e026049d157132e:
>
> clk: exynos5420: Add 5800 specific clocks (2014-05-19 22:15:08 +0900)
>
> ----------------------------------------------------------------
> Samsung clock updates for 3.16
>
> In this time, it is having dependency with arch/arm/ for 3.16,
> I pulled them into samsung tree from Tomasz under agreement from Mike.
>
> - Pull for_3.16/exynos5260 from Tomasz Figa:
>
> "This pull request contains patches preparing Samsung Common Clock
> Framework
> helpers to support Exynos5260 by adding support for multiple clock
> providers
> and then adding clock driver for Exynos5260."
>
> - Pull for_3.16/clk_fixes_non_critical from Tomasz Figa:
>
> "This pull requests contains a number of non-critical fixes for Samsung
> clock
> framework and drivers, including:
> 1) a series of fixes for Exynos5420 to correct clock definitions and make
> the
> driver closer to the documentation,
> 2) several missing clocks and clock IDs added to Exynos4, Exynos5250 and
> Exynos5420 drivers,
> 3) fix for incorrect initialization of clock table with NULL,
> 4) compiler warning fix."
>
> - Pull for_3.16/clk_cleanup from Tomasz Figa:
>
> "This pull requests contains minor clean-up related to Samsung clock
> support, including:
> 1) move Kconfig entries of Samsung clock drivers to drivers/clk,
> 2) compile drivers/clk/samsung conditionally when COMMON_CLK_SAMSUNG is
> selected,
> 3) remove obsolete Kconfig lines after moving s3c24xx to CCF."
>
> - Pull for_3.16/exynos3250 from Tomasz Figa:
>
> "This small pull request contains a patch adding clock driver for
> Exynos3250,
> which depends on previous pull requests in this series."
>
> - add dt bindings for exynos3250 clock
> - add exynos5800 specific clocks in current exynos5420 clock
>
> Note that this branch is based on s3c24xx ccf branch
Hi,
Merged into next/soc. In the future, you can probably just send up topic
branches like these directly, no need to merge them together just to send them
up.
-Olof
next prev parent reply other threads:[~2014-05-29 18:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-20 1:11 [GIT PULL 2/5] Samsung clock updates for 3.16 Kukjin Kim
2014-05-22 5:31 ` Olof Johansson
2014-05-22 9:56 ` Tomasz Figa
2014-05-22 11:42 ` Kukjin Kim
2014-05-29 18:17 ` Olof Johansson [this message]
2014-05-30 1:18 ` 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=20140529181708.GA18481@quad.lixom.net \
--to=olof@lixom.net \
--cc=arm@kernel.org \
--cc=arnd@arndb.de \
--cc=kgene.kim@samsung.com \
--cc=khilman@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=t.figa@samsung.com \
/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