All of lore.kernel.org
 help / color / mirror / Atom feed
From: Heiko Stuebner <heiko@sntech.de>
To: Elaine Zhang <zhangqing@rock-chips.com>
Cc: xf@rock-chips.com, mturquette@baylibre.com, sboyd@codeaurora.org,
	linux-clk@vger.kernel.org, huangtao@rock-chips.com,
	xxx@rock-chips.com, linux-rockchip@lists.infradead.org,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3 0/4] make some special clk as critical_clocks
Date: Fri, 02 Jun 2017 16:10:19 +0200	[thread overview]
Message-ID: <2347847.YaA7RMd5sr@phil> (raw)
In-Reply-To: <1493710446-7203-1-git-send-email-zhangqing@rock-chips.com>

Am Dienstag, 2. Mai 2017, 15:34:02 CEST schrieb Elaine Zhang:
> change in V3:
> reword the commit message,explain why the specific clocks are need to be critical.
> 
> change in v2:
> fix up some clks which have their own driver, not need to set as critical clocks
> 
> Elaine Zhang (4):
>   clk: rockchip: rk3036: make pclk_ddrupctl as critical_clock
>   clk: rockchip: rk3228: make noc and some special clk as
>     critical_clocks
>   clk: rockchip: rk3288: make noc and some special clk as
>     critical_clocks
>   clk: rockchip: rk3368: make some special clk as critical_clocks

applied all 4 for 4.13


Thanks
Heiko

WARNING: multiple messages have this Message-ID (diff)
From: heiko@sntech.de (Heiko Stuebner)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 0/4] make some special clk as critical_clocks
Date: Fri, 02 Jun 2017 16:10:19 +0200	[thread overview]
Message-ID: <2347847.YaA7RMd5sr@phil> (raw)
In-Reply-To: <1493710446-7203-1-git-send-email-zhangqing@rock-chips.com>

Am Dienstag, 2. Mai 2017, 15:34:02 CEST schrieb Elaine Zhang:
> change in V3:
> reword the commit message,explain why the specific clocks are need to be critical.
> 
> change in v2:
> fix up some clks which have their own driver, not need to set as critical clocks
> 
> Elaine Zhang (4):
>   clk: rockchip: rk3036: make pclk_ddrupctl as critical_clock
>   clk: rockchip: rk3228: make noc and some special clk as
>     critical_clocks
>   clk: rockchip: rk3288: make noc and some special clk as
>     critical_clocks
>   clk: rockchip: rk3368: make some special clk as critical_clocks

applied all 4 for 4.13


Thanks
Heiko

  parent reply	other threads:[~2017-06-02 14:10 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-02  7:34 [PATCH v3 0/4] make some special clk as critical_clocks Elaine Zhang
2017-05-02  7:34 ` Elaine Zhang
2017-05-02  7:34 ` [PATCH v3 1/4] clk: rockchip: rk3036: make pclk_ddrupctl as critical_clock Elaine Zhang
2017-05-02  7:34   ` Elaine Zhang
2017-05-02  7:34 ` [PATCH v3 2/4] clk: rockchip: rk3228: make noc and some special clk as critical_clocks Elaine Zhang
2017-05-02  7:34   ` Elaine Zhang
2017-05-02  7:34   ` Elaine Zhang
2017-05-02  7:34 ` [PATCH v3 3/4] clk: rockchip: rk3288: " Elaine Zhang
2017-05-02  7:34   ` Elaine Zhang
2017-05-02  7:34   ` Elaine Zhang
2017-05-02  7:34 ` [PATCH v3 4/4] clk: rockchip: rk3368: make " Elaine Zhang
2017-05-02  7:34   ` Elaine Zhang
2017-06-02 14:10 ` Heiko Stuebner [this message]
2017-06-02 14:10   ` [PATCH v3 0/4] " Heiko Stuebner

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=2347847.YaA7RMd5sr@phil \
    --to=heiko@sntech.de \
    --cc=huangtao@rock-chips.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=mturquette@baylibre.com \
    --cc=sboyd@codeaurora.org \
    --cc=xf@rock-chips.com \
    --cc=xxx@rock-chips.com \
    --cc=zhangqing@rock-chips.com \
    /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.