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: Wed, 14 May 2014 22:20:14 +0200	[thread overview]
Message-ID: <5373CFFE.1000209@gmail.com> (raw)
In-Reply-To: <20140514201313.19795.35617@quantum>

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.

> 
>>
>> How do you think? Basically I need your agreement for it.
> 
> Based on the above pull requests I do not see the need for changing how
> code gets merged.

As long as there are no dependencies on arch code and series being
applied do not touch arch code, this is perfectly fine. Unfortunately
this is rarely the case, at least for Samsung platforms and at least for
now. After we finish with arch clean-up and move all code to appropriate
subsystems, it should become easier, though.

Best regards,
Tomasz

  reply	other threads:[~2014-05-14 20:20 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 [this message]
2014-05-14 22:07       ` Mike Turquette
2014-05-14 22:16         ` Tomasz Figa
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=5373CFFE.1000209@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).