From: Tomasz Figa <tomasz.figa@gmail.com>
To: Abhilash Kesavan <a.kesavan@samsung.com>,
linux-samsung-soc@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
catalin.marinas@arm.com
Cc: naveenkrishna.ch@gmail.com, kesavan.abhilash@gmail.com
Subject: Re: [PATCH v5 0/8] arch: arm64: Enable support for Samsung Exynos7 SoC
Date: Mon, 22 Sep 2014 10:52:39 +0200 [thread overview]
Message-ID: <541FE357.5090000@gmail.com> (raw)
In-Reply-To: <1411361228-18279-1-git-send-email-a.kesavan@samsung.com>
Hi Abhilash,
On 22.09.2014 06:47, Abhilash Kesavan wrote:
> Changes since v4:
> - Fixed comments from Tomasz Figa:
> - Changed the namespace prefix from exynos to samsung
> - Defined bindings to take all input clocks
> - Sorted the Kconfig entries alphabetically in clock Makefile
> - Used consistent 1 tab line breaks across the clock file
> - Statically initialized the samsung_cmu_info struct
> - Enabled exynos7 in the arm64 defconfig as per Catalin Marinas' comment.
> - Added Kukjin Kim's ack along with Thomas Abraham's tested and reviewed tags.
>
The clock patches look good to me, but since they are doing quite a lot
of code moving I'd prefer to take them through clk tree. Based on the
fact that there are no code dependencies between clock patches and
remaining ones and Exynos7 is a new material for 3.18, I'm inclined to
apply them to my tree if nobody minds.
Best regards,
Tomasz
WARNING: multiple messages have this Message-ID (diff)
From: tomasz.figa@gmail.com (Tomasz Figa)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v5 0/8] arch: arm64: Enable support for Samsung Exynos7 SoC
Date: Mon, 22 Sep 2014 10:52:39 +0200 [thread overview]
Message-ID: <541FE357.5090000@gmail.com> (raw)
In-Reply-To: <1411361228-18279-1-git-send-email-a.kesavan@samsung.com>
Hi Abhilash,
On 22.09.2014 06:47, Abhilash Kesavan wrote:
> Changes since v4:
> - Fixed comments from Tomasz Figa:
> - Changed the namespace prefix from exynos to samsung
> - Defined bindings to take all input clocks
> - Sorted the Kconfig entries alphabetically in clock Makefile
> - Used consistent 1 tab line breaks across the clock file
> - Statically initialized the samsung_cmu_info struct
> - Enabled exynos7 in the arm64 defconfig as per Catalin Marinas' comment.
> - Added Kukjin Kim's ack along with Thomas Abraham's tested and reviewed tags.
>
The clock patches look good to me, but since they are doing quite a lot
of code moving I'd prefer to take them through clk tree. Based on the
fact that there are no code dependencies between clock patches and
remaining ones and Exynos7 is a new material for 3.18, I'm inclined to
apply them to my tree if nobody minds.
Best regards,
Tomasz
next prev parent reply other threads:[~2014-09-22 8:52 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-22 4:47 [PATCH v5 0/8] arch: arm64: Enable support for Samsung Exynos7 SoC Abhilash Kesavan
2014-09-22 4:47 ` Abhilash Kesavan
2014-09-22 4:47 ` [PATCH v5 1/8] clk: samsung: add support for 145xx and 1460x PLLs Abhilash Kesavan
2014-09-22 4:47 ` Abhilash Kesavan
2014-09-22 4:47 ` [PATCH v5 2/8] clk: samsung: Factor out the common code to clk.c Abhilash Kesavan
2014-09-22 4:47 ` Abhilash Kesavan
2014-09-22 4:47 ` [PATCH v5 3/8] clk: samsung: Add fixed_factor_clocks field to struct exynos_cmu_info Abhilash Kesavan
2014-09-22 4:47 ` Abhilash Kesavan
2014-09-22 4:47 ` [PATCH v5 4/8] clk: samsung: add initial clock support for Exynos7 SoC Abhilash Kesavan
2014-09-22 4:47 ` Abhilash Kesavan
2014-09-22 4:47 ` [PATCH v5 5/8] arm64: dts: Add initial device tree support for EXYNOS7 Abhilash Kesavan
2014-09-22 4:47 ` Abhilash Kesavan
2014-09-22 4:47 ` [PATCH v5 6/8] arm64: exynos7: Enable ARMv8 based Exynos7 (SoC) support Abhilash Kesavan
2014-09-22 4:47 ` Abhilash Kesavan
2014-09-22 4:47 ` [PATCH v5 7/8] arm64: Enable Exynos7 SOC in the defconfig Abhilash Kesavan
2014-09-22 4:47 ` Abhilash Kesavan
2014-09-22 4:47 ` [PATCH v5 8/8] arm64: dts: add <dt-bindings/> symlink Abhilash Kesavan
2014-09-22 4:47 ` Abhilash Kesavan
2014-09-23 7:46 ` Chanho Park
2014-09-23 7:46 ` Chanho Park
2014-09-23 8:54 ` Abhilash Kesavan
2014-09-23 8:54 ` Abhilash Kesavan
2014-09-22 8:52 ` Tomasz Figa [this message]
2014-09-22 8:52 ` [PATCH v5 0/8] arch: arm64: Enable support for Samsung Exynos7 SoC Tomasz Figa
2014-09-30 15:12 ` Abhilash Kesavan
2014-09-30 15:12 ` Abhilash Kesavan
2014-09-30 15:56 ` Tomasz Figa
2014-09-30 15:56 ` Tomasz Figa
2014-10-07 4:16 ` Kukjin Kim
2014-10-07 4:16 ` Kukjin Kim
2014-10-08 5:48 ` Abhilash Kesavan
2014-10-08 5:48 ` Abhilash Kesavan
2014-10-24 14:32 ` Abhilash Kesavan
2014-10-24 14:32 ` Abhilash Kesavan
2014-10-27 16:47 ` Sylwester Nawrocki
2014-10-27 16:47 ` Sylwester Nawrocki
2014-09-23 7:50 ` Chanho Park
2014-09-23 7:50 ` Chanho Park
2014-09-23 8:48 ` Abhilash Kesavan
2014-09-23 8:48 ` Abhilash Kesavan
2014-09-30 15:15 ` Abhilash Kesavan
2014-09-30 15:15 ` Abhilash Kesavan
2014-09-30 15:50 ` Catalin Marinas
2014-09-30 15:50 ` Catalin Marinas
2014-10-08 5:46 ` Abhilash Kesavan
2014-10-08 5:46 ` Abhilash Kesavan
-- strict thread matches above, loose matches on Subject: below --
2014-09-22 4:34 Abhilash Kesavan
2014-09-22 4:34 ` Abhilash Kesavan
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=541FE357.5090000@gmail.com \
--to=tomasz.figa@gmail.com \
--cc=a.kesavan@samsung.com \
--cc=catalin.marinas@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=kesavan.abhilash@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=naveenkrishna.ch@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.