From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: Magnus Damm <magnus.damm@gmail.com>
Cc: Wolfram Sang <wsa@the-dreams.de>,
linux-kernel <linux-kernel@vger.kernel.org>,
Kevin Hilman <khilman@linaro.org>, Arnd Bergmann <arnd@arndb.de>,
SH-Linux <linux-sh@vger.kernel.org>,
"Simon Horman [Horms]" <horms@verge.net.au>,
John Stultz <john.stultz@linaro.org>,
Olof Johansson <olof@lixom.net>
Subject: Re: [PATCH V6 0/3] clocksource: Consolidate SH and ARM mach-shmobile Kconfig bits
Date: Mon, 24 Feb 2014 23:51:19 +0100 [thread overview]
Message-ID: <530BCCE7.7060902@linaro.org> (raw)
In-Reply-To: <CANqRtoT6+6no5fT-6o7jD9k0hF+mMvU4z0ZmUCLksOsJTS0X8Q@mail.gmail.com>
On 02/24/2014 11:48 PM, Magnus Damm wrote:
> On Thu, Feb 20, 2014 at 5:47 PM, Daniel Lezcano
> <daniel.lezcano@linaro.org> wrote:
>> On 02/17/2014 09:55 PM, Wolfram Sang wrote:
>>>
>>> This is V6 of the SH and ARM mach-shmobile clocksource Kconfig
>>> consolidation
>>> series. It is a rebased version of V5 (which did not get any comments) on
>>> top
>>> of the latest renesas/devel tag. This series is not just an optimization,
>>> it
>>> also makes it possible to enable the clocksource for the r7s72100
>>> platform.
>>> Without it, the current kernel is hardly usable for these devices at the
>>> moment
>>> (broken userland). So, it would be nice to have the series in 3.15. For
>>> more
>>> details, I quote the cover-letter from Magnus for V5 at the end. I
>>> successfully
>>> tested the patches on r7s72100 and r8a7791 platforms. The branch can be
>>> found
>>> here:
>>>
>>> git://git.kernel.org/pub/scm/linux/kernel/git/wsa/linux.git
>>> renesas/rework-clock-configs
>>
>>
>> Hi Wolfram,
>>
>> actually I was waiting for Magnus to send me the patchset respinned against
>> timers/core [1].
>
> Hi Daniel,
>
> Thanks for your help and my apologies for this confusion. I moved
> house during December and a couple of things got dropped including
> this one.
No problem, that happens ;)
>> So if you mind, please refresh the series against timers/core as this series
>> does not apply for my tree.
>
> I noticed that Wolfram picked it up, thanks to both of you - I
> appreciate your help!
Thanks to Wolfram.
-- Daniel
--
<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
prev parent reply other threads:[~2014-02-24 22:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-17 20:55 [PATCH V6 0/3] clocksource: Consolidate SH and ARM mach-shmobile Kconfig bits Wolfram Sang
2014-02-17 20:55 ` [PATCH V6 1/3] clocksource: Add Kconfig entries for CMT, MTU2, TMU and STI Wolfram Sang
2014-02-17 20:55 ` [PATCH V6 2/3] ARM: shmobile: Remove CMT, TMU and STI Kconfig entries Wolfram Sang
2014-02-17 20:55 ` [PATCH V6 3/3] sh: Remove Kconfig entries for TMU, CMT and MTU2 Wolfram Sang
2014-02-20 8:47 ` [PATCH V6 0/3] clocksource: Consolidate SH and ARM mach-shmobile Kconfig bits Daniel Lezcano
2014-02-20 11:41 ` Wolfram Sang
2014-02-24 22:48 ` Magnus Damm
2014-02-24 22:51 ` Daniel Lezcano [this message]
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=530BCCE7.7060902@linaro.org \
--to=daniel.lezcano@linaro.org \
--cc=arnd@arndb.de \
--cc=horms@verge.net.au \
--cc=john.stultz@linaro.org \
--cc=khilman@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=olof@lixom.net \
--cc=wsa@the-dreams.de \
/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