public inbox for linux-arm-kernel@lists.infradead.org 
 help / color / mirror / Atom feed
From: daniel.lezcano@linaro•org (Daniel Lezcano)
To: linux-arm-kernel@lists•infradead.org
Subject: [GIT PULL 4/5] Samsung exynos_mct update for v3.17
Date: Tue, 22 Jul 2014 19:32:16 +0200	[thread overview]
Message-ID: <53CEA020.309@linaro.org> (raw)
In-Reply-To: <01b601cfa59c$12c2c7f0$384857d0$@samsung.com>

On 07/22/2014 12:59 PM, Kukjin Kim wrote:
> Daniel Lezcano wrote:
>>
>> On 07/20/2014 12:06 AM, Olof Johansson wrote:
>>> On Sat, Jul 19, 2014 at 09:52:52AM +0900, Kukjin Kim wrote:
>>>> Note that this is also based on 3.16-rc5 because of dependency with
>>>> previous samsung fixes including exynos_mct already merged in
>>>> mainline during -rc.
>>>>
>>>> The following changes since commit 1795cd9b3a91d4b5473c97f491d63892442212ab:
>>>>
>>>>     Linux 3.16-rc5 (2014-07-13 14:04:33 -0700)
>>>>
>>>> are available in the git repository at:
>>>>
>>>
>>>> git://git.kernel.org/pub/scm/linux/kernel/git/kgene/linux-samsung.git
>>>> tags/exynos-mct
>>>>
>>>> for you to fetch changes up to 1a631118c1d085fe162f3b6d44f710c72206ef2d:
>>>>
>>>>     clocksource: exynos_mct: Only use 32-bits where possible
>>>> (2014-07-19 03:07:52 +0900)
>>>>
>>>> ----------------------------------------------------------------
>>>> exynos_mct update for v3.17
>>>> - only use 32-bit access for performance benefits on exynos
>>>>     32-bit system and this means ARCH timer should be supported
>>>>     on exynos 64-bit system instead of current MCT.
>>>> - use readl_relaxed/writel_relaxed to consistently use the
>>>>     proper functions in exynos_mct.
>>>
>>> There's no reason for these to go through arm-soc, is there? They should
>>> go through the clocksource tree (Daniel Lezcano / Thomas Gleixner). They
>>> also lack acks from them if they for some reason need to go through arm-soc.
>>
> Olof, you're right. The branch has no dependency with arm-soc so I agreed.
>
>> Yes, that's right. Furthermore I have been discussing with Doug about
>> these patches before.
>>
>> Kukjin, is there any dependency on these patches ?
>>
> Yeah, Daniel, it should be handled in the clocksource tree so how should I do
> for it?

I can pull your branch v3.17-next/mct-exynos and you drop the merge from 
this branch in your master ?



-- 
  <http://www.linaro.org/> Linaro.org ? Open source software for ARM SoCs

Follow Linaro:  <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog

  reply	other threads:[~2014-07-22 17:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-19  0:52 [GIT PULL 4/5] Samsung exynos_mct update for v3.17 Kukjin Kim
2014-07-19 22:06 ` Olof Johansson
2014-07-21  8:47   ` Daniel Lezcano
2014-07-22 10:59     ` Kukjin Kim
2014-07-22 17:32       ` Daniel Lezcano [this message]
2014-07-22 23:33         ` Kukjin Kim
2014-07-23  8:03           ` Daniel Lezcano

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=53CEA020.309@linaro.org \
    --to=daniel.lezcano@linaro$(echo .)org \
    --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