linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: sboyd@codeaurora.org (Stephen Boyd)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] clk: rockchip: Add pclk_peri to critical clocks on RK3066/RK3188
Date: Thu, 10 Sep 2015 13:51:55 -0700	[thread overview]
Message-ID: <20150910205155.GC15099@codeaurora.org> (raw)
In-Reply-To: <994A907A-09DB-419C-9BD5-772B379D02B3@mniewoehner.de>

On 09/10, Michael Niewoehner wrote:
> 
> Am 10.09.2015 um 09:05 schrieb Romain Perier <romain.perier@gmail.com>:
> 
> > It was based on linux-next few weeks ago. I will rebase it today and send a v3.
> > 
> > 2015-09-09 23:47 GMT+02:00 Stephen Boyd <sboyd@codeaurora.org>:
> >> On 09/09, Romain Perier wrote:
> >>> so, which of you does take the patch for -rc1 ?
> >>> 
> >> Is there some other patch out there that's also needed?
> > 
> > No, that's a single patch.
> > 
> > Romain
> > 
> 
> Hi Stephen,
> 
> Romain?s patch was applied after mine in his github tree so you?ll need to apply that first: [PATCH v3] clk: rockchip: add pclk_cpu to the list of rk3188 critical clocks
> 

Ah ok. Consider both applied to clk-fixes.

-- 
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project

      reply	other threads:[~2015-09-10 20:51 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-23  9:32 [PATCH v2] clk: rockchip: Add pclk_peri to critical clocks on RK3066/RK3188 Romain Perier
2015-08-31 14:42 ` Romain Perier
2015-09-04  6:50   ` Romain Perier
2015-09-04 16:24     ` Stephen Boyd
2015-09-05 16:12       ` Romain Perier
2015-09-09 17:58         ` Romain Perier
2015-09-09 21:47           ` Stephen Boyd
2015-09-10  7:05             ` Romain Perier
2015-09-10 16:40               ` Michael Niewoehner
2015-09-10 20:51                 ` Stephen Boyd [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=20150910205155.GC15099@codeaurora.org \
    --to=sboyd@codeaurora.org \
    --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).