linux-clk.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Boyd <sboyd@kernel.org>
To: Paul Cercueil <paul@crapouillou.net>
Cc: Michael Turquette <mturquette@baylibre.com>,
	linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] clk: ingenic: jz4740: Fix gating of UDC clock
Date: Tue, 29 Jan 2019 13:16:11 -0800	[thread overview]
Message-ID: <154879657128.136743.2772783193736020021@swboyd.mtv.corp.google.com> (raw)
In-Reply-To: <1548789745.2531.0@crapouillou.net>

Quoting Paul Cercueil (2019-01-29 11:22:25)
> Hi,
> 
> Le mar. 29 janv. 2019 à 15:13, Stephen Boyd <sboyd@kernel.org> a 
> écrit :
> > Quoting Paul Cercueil (2019-01-25 11:24:58)
> >>  Hi,
> >> 
> >> 
> >>  On Fri, Jan 25, 2019 at 3:55 PM, Stephen Boyd <sboyd@kernel.org> 
> >> wrote:
> >>  > Quoting Paul Cercueil (2019-01-25 07:34:36)
> >>  >>  The UDC clock is gated when the bit is cleared, not when it is 
> >> set.
> >>  >>
> >>  >>  Signed-off-by: Paul Cercueil <paul@crapouillou.net
> >>  >> <mailto:paul@crapouillou.net>>
> >>  >>  Tested-by: Artur Rojek <contact@artur-rojek.eu
> >>  >> <mailto:contact@artur-rojek.eu>>
> >>  >>  ---
> >>  >
> >>  > Any Fixes tag for this?
> >>  >
> >> 
> >>  Fixes: 2b555a4b9cae
> >> 
> >>  Should I resend?
> >> 
> > 
> > No need to resend. Is this fixing something that's broken in the 
> > v5.0-rc
> > series? I'm trying to understand if this is a critical fix or a
> > non-critical fix that can bake until the next release cycle.
> 
> It's been broken for one year and nobody noticed, it can wait for 5.1.
> 

Ok, thanks!


  reply	other threads:[~2019-01-29 21:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-25 15:34 [PATCH] clk: ingenic: jz4740: Fix gating of UDC clock Paul Cercueil
2019-01-25 18:55 ` Stephen Boyd
2019-01-25 19:24   ` Paul Cercueil
2019-01-29 18:13     ` Stephen Boyd
2019-01-29 19:22       ` Paul Cercueil
2019-01-29 21:16         ` Stephen Boyd [this message]
2019-02-05 21:32 ` Stephen Boyd

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=154879657128.136743.2772783193736020021@swboyd.mtv.corp.google.com \
    --to=sboyd@kernel.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mturquette@baylibre.com \
    --cc=paul@crapouillou.net \
    /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).