linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: tomasz.figa@gmail.com (Tomasz Figa)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 1/4] Samsung clock Exynos5260 support for v3.16
Date: Thu, 15 May 2014 00:16:04 +0200	[thread overview]
Message-ID: <5373EB24.8000306@gmail.com> (raw)
In-Reply-To: <20140514220744.19795.64527@quantum>

On 15.05.2014 00:07, Mike Turquette wrote:
> Quoting Tomasz Figa (2014-05-14 13:20:14)
>> Hi Mike,
>>
>> On 14.05.2014 22:13, Mike Turquette wrote:
>>> Quoting Kukjin Kim (2014-05-14 12:59:22)
>>>> On 05/15/14 03:03, Tomasz Figa wrote:
>>>>
>>>> Hi Mike,
>>>>
>>>> I've talked to Tomasz about current samsung related clock stuff. Since 
>>>> they are mostly having dependency on samsung tree now not clock core 
>>>> stuff, so would be better if it could be sent to upstream via samsung 
>>>> tree. And as you know, updating arch/arm/ and clock stuff are usually 
>>>> required for adding new SoC or supporting CCF newly...
>>>
>>> The Samsung clk pull requests only touch two arch/arm Kconfig files and
>>> one dtsi file. That's not a lot of arch/arm churn. Is there a strong
>>> reason that this needs to go through the samsung/arm-soc trees?
>>> Otherwise it should continue to go through the clk tree.
>>
>> Obviously they are patches for Samsung clock drivers. ;)
>>
>> The issue here is that there is a number of patches already merged in
>> Samsung tree on which the patches discussed here depend.
> 
> OK, I think I misread the original email. I thought you were asking for
> future pull requests to go through the samsung tree, but you only mean
> the ones in this thread. No problem there.
> 
> Acked-by: Mike Turquette <mturquette@linaro.org>

Thanks.

As you probably noticed with my pull request for 3.15, we've been
getting quite a lot of burden due to dependencies between arch and clk
patches lastly, but this is inevitable when we are moving things out of
arch.

The good news is that after patches from this pull request series, we
will end up with just one, more or less active platform (s5pv210) that
needs to be converted (and work already in progress).

Best regards,
Tomasz

  reply	other threads:[~2014-05-14 22:16 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-14 18:03 [GIT PULL 1/4] Samsung clock Exynos5260 support for v3.16 Tomasz Figa
2014-05-14 18:03 ` [GIT PULL 2/4] Samsung clock non-critical fixes " Tomasz Figa
2014-05-14 18:03 ` [GIT PULL 3/4] Samsung clock clean-up " Tomasz Figa
2014-05-14 18:03 ` [GIT PULL 4/4] Samsung clock support for Exynos3250 " Tomasz Figa
2014-05-14 19:59 ` [GIT PULL 1/4] Samsung clock Exynos5260 support " Kukjin Kim
2014-05-14 20:13   ` Mike Turquette
2014-05-14 20:20     ` Tomasz Figa
2014-05-14 22:07       ` Mike Turquette
2014-05-14 22:16         ` Tomasz Figa [this message]
2014-05-15 21:11           ` Kukjin Kim
2014-05-16 23:57             ` 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=5373EB24.8000306@gmail.com \
    --to=tomasz.figa@gmail.com \
    --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).