From: Heiko Stuebner <heiko@sntech.de>
To: Elaine Zhang <zhangqing@rock-chips.com>
Cc: mturquette@baylibre.com, sboyd@codeaurora.org, xf@rock-chips.com,
robh+dt@kernel.org, mark.rutland@arm.com,
linux-clk@vger.kernel.org, huangtao@rock-chips.com,
xxx@rock-chips.com, cl@rock-chips.com,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v5 2/4] dt-bindings: add bindings for rk3328 clock controller
Date: Thu, 05 Jan 2017 13:42:31 +0100 [thread overview]
Message-ID: <3178718.5FUeKukzJD@phil> (raw)
In-Reply-To: <1482979511-6847-3-git-send-email-zhangqing@rock-chips.com>
Am Donnerstag, 29. Dezember 2016, 10:45:09 CET schrieb Elaine Zhang:
> Add devicetree bindings for Rockchip cru which found on
> Rockchip SoCs.
>
> Changes in v4:
> dropping the "rockchip,cru" and "syscon" properties for bindings of rk3328
>
> Signed-off-by: Elaine Zhang <zhangqing@rock-chips.com>
applied for 4.11 with Rob's Ack
WARNING: multiple messages have this Message-ID (diff)
From: heiko@sntech.de (Heiko Stuebner)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v5 2/4] dt-bindings: add bindings for rk3328 clock controller
Date: Thu, 05 Jan 2017 13:42:31 +0100 [thread overview]
Message-ID: <3178718.5FUeKukzJD@phil> (raw)
In-Reply-To: <1482979511-6847-3-git-send-email-zhangqing@rock-chips.com>
Am Donnerstag, 29. Dezember 2016, 10:45:09 CET schrieb Elaine Zhang:
> Add devicetree bindings for Rockchip cru which found on
> Rockchip SoCs.
>
> Changes in v4:
> dropping the "rockchip,cru" and "syscon" properties for bindings of rk3328
>
> Signed-off-by: Elaine Zhang <zhangqing@rock-chips.com>
applied for 4.11 with Rob's Ack
next prev parent reply other threads:[~2017-01-05 12:42 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-29 2:45 [PATCH v5 0/4] clk: rockchip: support clk controller for rk3328 SoC Elaine Zhang
2016-12-29 2:45 ` Elaine Zhang
2016-12-29 2:45 ` [PATCH v5 1/4] clk: rockchip: add dt-binding header for rk3328 Elaine Zhang
2016-12-29 2:45 ` Elaine Zhang
2016-12-29 2:45 ` Elaine Zhang
2017-01-05 12:39 ` Heiko Stuebner
2017-01-05 12:39 ` Heiko Stuebner
2017-01-05 12:39 ` Heiko Stuebner
2017-01-05 12:54 ` Heiko Stuebner
2017-01-05 12:54 ` Heiko Stuebner
2017-01-05 12:54 ` Heiko Stuebner
2016-12-29 2:45 ` [PATCH v5 2/4] dt-bindings: add bindings for rk3328 clock controller Elaine Zhang
2016-12-29 2:45 ` Elaine Zhang
2017-01-03 20:41 ` Rob Herring
2017-01-03 20:41 ` Rob Herring
2017-01-03 20:41 ` Rob Herring
2017-01-05 12:42 ` Heiko Stuebner [this message]
2017-01-05 12:42 ` Heiko Stuebner
2016-12-29 2:45 ` [PATCH v5 3/4] clk: rockchip: add new pll-type for rk3328 Elaine Zhang
2016-12-29 2:45 ` Elaine Zhang
2016-12-31 12:53 ` Heiko Stuebner
2016-12-31 12:53 ` Heiko Stuebner
2016-12-29 2:45 ` [PATCH v5 4/4] clk: rockchip: add clock controller " Elaine Zhang
2016-12-29 2:45 ` Elaine Zhang
2017-01-05 12:53 ` Heiko Stuebner
2017-01-05 12:53 ` 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=3178718.5FUeKukzJD@phil \
--to=heiko@sntech.de \
--cc=cl@rock-chips.com \
--cc=devicetree@vger.kernel.org \
--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=mark.rutland@arm.com \
--cc=mturquette@baylibre.com \
--cc=robh+dt@kernel.org \
--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.