From: Olof Johansson <olof@lixom.net>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: "linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"arm@kernel.org" <arm@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/4] clocksource: nomadik-mtu: fix up clocksource/timer
Date: Fri, 26 Apr 2013 17:12:10 -0700 [thread overview]
Message-ID: <20130427001210.GA1714@quad.lixom.net> (raw)
In-Reply-To: <CACRpkdYWSM0BK77qWbQWh0xsN+Ps95Q70zG-GE98MYvThrky2A@mail.gmail.com>
On Sat, Apr 20, 2013 at 03:19:43PM +0200, Linus Walleij wrote:
> ARM SoC folks:
>
> On Sat, Apr 20, 2013 at 3:08 PM, Linus Walleij <linus.walleij@linaro.org> wrote:
>
> > The Nomadik clocksource driver has had a bad define making it
> > impossible to use it for sched_clock() for a while. Fix this
> > and also enable it for the Nomadik.
> >
> > Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
>
> This one should go to fixes ASAP, could you pick it to your fixes
> branch? It could be tagged stable if desired - this only affects the
> Nomadik which works just OK on jiffies so it's really no big regression.
> The Ux500 does not use the MTU for sched_clock().
Ok, applied on top of next/multiplatform, seems to be what it's based on.
Tagging as stable is up to you as platform owner. :) Since it won't directly
apply to older kernels you might be better of submitting it to Greg separately.
-Olof
next prev parent reply other threads:[~2013-04-27 0:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-20 13:08 Linus Walleij
2013-04-20 13:19 ` Linus Walleij
2013-04-27 0:12 ` Olof Johansson [this message]
2013-04-29 9:05 ` Linus Walleij
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=20130427001210.GA1714@quad.lixom.net \
--to=olof@lixom.net \
--cc=arm@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®