From: horms@verge.net.au (Simon Horman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/4] ARM: shmobile: sh73a0: fix Z and ZG clock hierarchy
Date: Tue, 26 Feb 2013 14:43:20 +0900 [thread overview]
Message-ID: <20130226054319.GA25356@verge.net.au> (raw)
In-Reply-To: <CANqRtoRjs=OxsoUQrcL6nJG-o1RpxefO3BrjBj_A2GV8HNW=qQ@mail.gmail.com>
On Tue, Feb 26, 2013 at 02:36:24PM +0900, Magnus Damm wrote:
> On Tue, Feb 26, 2013 at 1:29 PM, Simon Horman <horms@verge.net.au> wrote:
> > On Fri, Feb 22, 2013 at 06:17:51PM +0100, Guennadi Liakhovetski wrote:
> >> Z and ZG clocks on sh73a0 have pll0 as their parent, not pll1.
> >
> > Thanks I have applied this to the soc5 branch and thus queued it up for v3.10.
> > Please let me know if you would prefer me to push it as a fix for v3.9.
> > And in that vein, if you regard it as -stable material.
>
> Thanks.
>
> Perhaps other people disagree, but I recommend not being so trigger
> happy with -stable unless it will potentially give us some upside.
> AFAIK there is no in-tree consumer of this clock anyway, so involving
> -stable without further testing seems like a lot of hassle with no
> real benefit.
If there is no in-tree consumer then it is not v3.9 or -stable material.
Thanks!
next prev parent reply other threads:[~2013-02-26 5:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-22 17:17 [PATCH/RFC 0/4] CPUFreq for kzm9g Guennadi Liakhovetski
2013-02-22 17:17 ` [PATCH 1/4] ARM: shmobile: sh73a0: fix Z and ZG clock hierarchy Guennadi Liakhovetski
2013-02-26 4:29 ` Simon Horman
2013-02-26 5:36 ` Magnus Damm
2013-02-26 5:43 ` Simon Horman [this message]
2013-02-26 6:09 ` Guennadi Liakhovetski
2013-02-26 12:15 ` Simon Horman
2013-02-22 17:17 ` [PATCH/RFC 2/4] ARM: shmobile: sh73a0: add support for adjusting CPU frequency Guennadi Liakhovetski
2013-02-22 17:17 ` [PATCH/RFC 3/4] ARM: shmobile: sh73a0: run sh73a0_clock_init() only once Guennadi Liakhovetski
2013-02-22 17:17 ` [PATCH 4/4] ARM: shmobile: kzm9g-reference: add CPUFreq support Guennadi Liakhovetski
2013-02-25 1:43 ` [PATCH/RFC 0/4] CPUFreq for kzm9g Simon Horman
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=20130226054319.GA25356@verge.net.au \
--to=horms@verge.net.au \
--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).