From: dianders@chromium.org (Doug Anderson)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 6/7] clk: rockchip: add binding id for ARMCLK
Date: Fri, 12 Sep 2014 17:10:46 -0700 [thread overview]
Message-ID: <CAD=FV=XWG1+PktkJUjSMaswRnJ-d6WVcf5AnVyKPp1=c4vn1eQ@mail.gmail.com> (raw)
In-Reply-To: <1410561030-19127-7-git-send-email-heiko@sntech.de>
Heiko,
On Fri, Sep 12, 2014 at 3:30 PM, Heiko Stuebner <heiko@sntech.de> wrote:
> Signed-off-by: Heiko Stuebner <heiko@sntech.de>
> ---
> include/dt-bindings/clock/rk3188-cru-common.h | 1 +
> include/dt-bindings/clock/rk3288-cru.h | 1 +
> 2 files changed, 2 insertions(+)
A little silly to say that I tested adding #defines, but it does
compile and later patches work...
Reviewed-by: Doug Anderson <dianders@chromium.org>
Tested-by: Doug Anderson <dianders@chromium.org>
next prev parent reply other threads:[~2014-09-13 0:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-12 22:30 [PATCH v2 0/7] ARM: Rockchip: add cpuclk handling - clock-tree part Heiko Stuebner
2014-09-12 22:30 ` [PATCH v2 1/7] clk: rockchip: fix rk3066 pll status register location Heiko Stuebner
2014-09-12 22:30 ` [PATCH v2 2/7] clk: rockchip: fix rk3288 " Heiko Stuebner
2014-09-12 23:46 ` Doug Anderson
2014-09-12 22:30 ` [PATCH v2 3/7] clk: rockchip: reparent aclk_cpu_pre to the gpll Heiko Stuebner
2014-09-12 22:30 ` [PATCH v2 4/7] clk: rockchip: make tightly bound armclk child-clocks read-only Heiko Stuebner
2014-09-12 23:52 ` Doug Anderson
2014-09-12 22:30 ` [PATCH v2 5/7] clk: rockchip: add new clock-type for the cpuclk Heiko Stuebner
2014-09-15 23:58 ` Doug Anderson
2014-09-16 0:49 ` Doug Anderson
2014-09-16 9:49 ` Karl Palsson
2014-09-16 1:00 ` Kever Yang
2014-09-16 4:37 ` Doug Anderson
2014-09-12 22:30 ` [PATCH v2 6/7] clk: rockchip: add binding id for ARMCLK Heiko Stuebner
2014-09-13 0:10 ` Doug Anderson [this message]
2014-09-12 22:30 ` [PATCH v2 7/7] clk: rockchip: switch to using the new cpuclk type for armclk 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='CAD=FV=XWG1+PktkJUjSMaswRnJ-d6WVcf5AnVyKPp1=c4vn1eQ@mail.gmail.com' \
--to=dianders@chromium.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 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.