All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Turquette <mturquette-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
To: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>,
	Thierry Reding
	<thierry.reding-RM9K5IK7kjKj5M59NBduVrNAH6kLmebB@public.gmane.org>
Cc: Prashant Gaikwad
	<pgaikwad-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>,
	Peter De Schrijver
	<pdeschrijver-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>,
	linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] clk: tegra: Allow PLLE training to succeed
Date: Fri, 22 Mar 2013 13:48:22 -0700	[thread overview]
Message-ID: <20130322204822.834.98314@quantum> (raw)
In-Reply-To: <51437655.1030008-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>

Quoting Stephen Warren (2013-03-15 12:28:21)
> On 03/14/2013 09:27 AM, Thierry Reding wrote:
> > Under some circumstances the PLLE needs to be retrained, in which case
> > access to the PMC registers is required. Fix this by passing a pointer
> > to the PMC registers instead of NULL when registering the PLLE clock.
> 
> Mike, I believe this patch is appropriate as a fix for v3.9. I assume
> you'll take it through the clock tree? Thanks.

Does this patch fix a crash or a documented failure?  Linus is being
more strict about taking fixes in the -rc cycles these days and knowing
exactly what behavior this fixes would be beneficial.

Thanks,
Mike

  parent reply	other threads:[~2013-03-22 20:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-14 15:27 [PATCH] clk: tegra: Allow PLLE training to succeed Thierry Reding
     [not found] ` <1363274825-2439-1-git-send-email-thierry.reding-RM9K5IK7kjKj5M59NBduVrNAH6kLmebB@public.gmane.org>
2013-03-15  9:28   ` Peter De Schrijver
2013-03-15 19:28   ` Stephen Warren
     [not found]     ` <51437655.1030008-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2013-03-22 20:48       ` Mike Turquette [this message]
2013-03-25 18:53         ` Thierry Reding
     [not found]           ` <20130325211304.4014.822@quantum>
2013-03-25 21:35             ` Thierry Reding

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=20130322204822.834.98314@quantum \
    --to=mturquette-qsej5fyqhm4dnm+yrofe0a@public.gmane.org \
    --cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=pdeschrijver-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org \
    --cc=pgaikwad-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org \
    --cc=swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org \
    --cc=thierry.reding-RM9K5IK7kjKj5M59NBduVrNAH6kLmebB@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.