From: Paul Mundt <lethal@linux-sh.org>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH] sh: propagate r_clk
Date: Mon, 01 Dec 2008 06:52:51 +0000 [thread overview]
Message-ID: <20081201065251.GA6339@linux-sh.org> (raw)
In-Reply-To: <20081201064033.28841.90287.sendpatchset@rx1.opensource.se>
On Mon, Dec 01, 2008 at 03:45:21PM +0900, Magnus Damm wrote:
> On Mon, Dec 1, 2008 at 3:42 PM, Paul Mundt <lethal@linux-sh.org> wrote:
> > On Mon, Dec 01, 2008 at 03:40:33PM +0900, Magnus Damm wrote:
> >> From: Magnus Damm <damm@igel.co.jp>
> >>
> >> Make sure the 32 KHz r_clk rate gets propagated correctly. Without
> >> this fix the clocks for RTC, CMT, KEYSC and RWDT are stuck at 0 Hz.
> >>
> >> Signed-off-by: Magnus Damm <damm@igel.co.jp>
> >
> > Does this apply to 2.6.28 also, or does it depend on your rate
> > propagation changes that are aimed at the merge window?
>
> 2.6.29 only, thanks.
>
Applied, thanks.
prev parent reply other threads:[~2008-12-01 6:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-01 6:40 [PATCH] sh: propagate r_clk Magnus Damm
2008-12-01 6:42 ` Paul Mundt
2008-12-01 6:45 ` Magnus Damm
2008-12-01 6:52 ` Paul Mundt [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=20081201065251.GA6339@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=linux-sh@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