From: s.nawrocki@samsung•com (Sylwester Nawrocki)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH v5 0/8] arch: arm64: Enable support for Samsung Exynos7 SoC
Date: Mon, 27 Oct 2014 17:47:29 +0100 [thread overview]
Message-ID: <544E7721.3040108@samsung.com> (raw)
In-Reply-To: <CAM4voanMX__N6=q8gg1LEGxqGTtByJXPdj+oAucHoyDh5ybaEA@mail.gmail.com>
Hi Abhilash,
On 24/10/14 16:32, Abhilash Kesavan wrote:
> On Wed, Oct 8, 2014 at 11:18 AM, Abhilash Kesavan
> <kesavan.abhilash@gmail•com> wrote:
>> On Tue, Oct 7, 2014 at 9:46 AM, Kukjin Kim <kgene@kernel•org> wrote:
>>> Tomasz Figa wrote:
>>>> On 30.09.2014 17:12, Abhilash Kesavan wrote:
>>>>> On Mon, Sep 22, 2014 at 2:22 PM, Tomasz Figa <tomasz.figa@gmail•com> wrote:
>>>>>>
>>>>>> 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.
>>>>>
>>>>> Will you be picking up the clock changes soon ?
>>>>
>>>> I'd like to do so. Kukjin, since clock changes are a part of this
>>>> series, might I have your Ack for them to be applied separately?
>>>>
>>> Sure, I'm fine so please go ahead with my ack on the changes.
>>>
>>> Acked-by: Kukjin Kim <kgene.kim@samsung•com>
>>>
>>> Thanks for your asking.
>>
>> Can you please pick up the clock changes now that Kukjin has ack'ed it.
>
> Sylwester, you mentioned in another thread that Tomasz might not be
> available for the next few days. Could you please consider applying
> the clock changes in this series to samsung clk-next if they look OK ?
>
> Please take a look at clock changes at
> http://www.spinics.net/lists/arm-kernel/msg370673.html too.
I've picked up patches from the $subject series. But please see my
comment the the second series you've pointed out with the link above.
If you decide to rearrange changes to exynos7-clk.h header file among
those two series I will drop that 4 patches. Perhaps you could gather
all pending exynos7 clk patches, fix any issues and send to me in one
series ?
I'd like to avoid modifying indices assigned to specific clocks in
subsequent patches, DT binding should be defined in advance and ideally
be specifying exact indices for each possible clock.
--
Thanks,
Sylwester
next prev parent reply other threads:[~2014-10-27 16:47 UTC|newest]
Thread overview: 24+ 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 ` [PATCH v5 1/8] clk: samsung: add support for 145xx and 1460x PLLs 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 ` [PATCH v5 3/8] clk: samsung: Add fixed_factor_clocks field to struct exynos_cmu_info 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 ` [PATCH v5 5/8] arm64: dts: Add initial device tree support for EXYNOS7 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 ` [PATCH v5 7/8] arm64: Enable Exynos7 SOC in the defconfig Abhilash Kesavan
2014-09-22 4:47 ` [PATCH v5 8/8] arm64: dts: add <dt-bindings/> symlink Abhilash Kesavan
2014-09-23 7:46 ` Chanho Park
2014-09-23 8:54 ` Abhilash Kesavan
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:56 ` Tomasz Figa
2014-10-07 4:16 ` Kukjin Kim
2014-10-08 5:48 ` Abhilash Kesavan
2014-10-24 14:32 ` Abhilash Kesavan
2014-10-27 16:47 ` Sylwester Nawrocki [this message]
2014-09-23 7:50 ` Chanho Park
2014-09-23 8:48 ` Abhilash Kesavan
2014-09-30 15:15 ` Abhilash Kesavan
2014-09-30 15:50 ` Catalin Marinas
2014-10-08 5:46 ` Abhilash Kesavan
-- strict thread matches above, loose matches on Subject: below --
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=544E7721.3040108@samsung.com \
--to=s.nawrocki@samsung$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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