From: Mike Turquette <mturquette@linaro.org>
To: heiko@sntech.de
Cc: dianders@chromium.org, sonnyrao@chromium.org,
addy.ke@rock-chips.com, cf@rock-chips.com, xjq@rock-chips.com,
hj@rock-chips.com, huangtao@rock-chips.com,
linux-rockchip@lists.infradead.org,
Kever Yang <kever.yang@rock-chips.com>,
devicetree@vger.kernel.org, Kumar Gala <galak@codeaurora.org>,
linux-kernel@vger.kernel.org,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Rob Herring <robh+dt@kernel.org>, Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/2] Add clock binding id for rk3288
Date: Thu, 25 Sep 2014 15:01:19 -0700 [thread overview]
Message-ID: <20140925220119.19023.81611@quantum> (raw)
In-Reply-To: <1411565795-26966-1-git-send-email-kever.yang@rock-chips.com>
Quoting Kever Yang (2014-09-24 06:36:33)
> This patch add some clock binding id for different modules
> that under development and going to send upstream.
>
> This patch also add the clock node in PD_VIDEO.
Applied both patches to clk-next and fixed up the comment block locally.
Regards,
Mike
>
>
> Kever Yang (2):
> clk: rockchip: add some needed clock binding id for rk3288
> clk: rockchip: use the clock id for nodes init
>
> drivers/clk/rockchip/clk-rk3288.c | 79 +++++++++++++++++++---------------
> include/dt-bindings/clock/rk3288-cru.h | 38 +++++++++++++++-
> 2 files changed, 82 insertions(+), 35 deletions(-)
>
> --
> 1.9.1
>
prev parent reply other threads:[~2014-09-25 22:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-24 13:36 [PATCH 0/2] Add clock binding id for rk3288 Kever Yang
[not found] ` <1411565795-26966-1-git-send-email-kever.yang-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2014-09-24 13:36 ` [PATCH 1/2] clk: rockchip: add some needed " Kever Yang
2014-09-24 14:06 ` Heiko Stübner
2014-09-25 22:01 ` Mike Turquette [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=20140925220119.19023.81611@quantum \
--to=mturquette@linaro.org \
--cc=addy.ke@rock-chips.com \
--cc=cf@rock-chips.com \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=galak@codeaurora.org \
--cc=heiko@sntech.de \
--cc=hj@rock-chips.com \
--cc=huangtao@rock-chips.com \
--cc=ijc+devicetree@hellion.org.uk \
--cc=kever.yang@rock-chips.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=sonnyrao@chromium.org \
--cc=xjq@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 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).