From: "Heiko Stübner" <heiko@sntech.de>
To: Xing Zheng <zhengxing@rock-chips.com>
Cc: linux-rockchip@lists.infradead.org, huangtao@rock-chips.com,
jay.xu@rock-chips.com, elaine.zhang@rock-chips.com,
dianders@chromium.org, devicetree@vger.kernel.org,
Stephen Boyd <sboyd@codeaurora.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>,
Michael Turquette <mturquette@baylibre.com>,
Mark Rutland <mark.rutland@arm.com>,
linux-clk@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v6 0/3] Add more clock compatible features and support the RK3399 clock
Date: Mon, 28 Mar 2016 14:59:59 +0200 [thread overview]
Message-ID: <4649399.g7v7zsVJik@diego> (raw)
In-Reply-To: <1459158697-8218-1-git-send-email-zhengxing@rock-chips.com>
Am Montag, 28. März 2016, 17:51:34 schrieb Xing Zheng:
> The patch series add support more mux parameters and multiple
> clock providers for the rockchip features of the clock framework,
> and support the clock controller for the RK3399.
applied all 3 for 4.7 with one change:
I've dropped the grf paragraph from the binding doc (as it is not used
anymore) and also dropped the gmac_phy_rx_clk input clock.
We can add these back once they are getting used in the future.
Heiko
next prev parent reply other threads:[~2016-03-28 12:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-28 9:51 [PATCH v6 0/3] Add more clock compatible features and support the RK3399 clock Xing Zheng
[not found] ` <1459158697-8218-1-git-send-email-zhengxing-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2016-03-28 9:51 ` [PATCH v6 1/3] dt-bindings: add bindings for rk3399 clock controller Xing Zheng
2016-03-28 9:51 ` [PATCH v6 2/3] clk: rockchip: add dt-binding header for rk3399 Xing Zheng
2016-03-28 12:59 ` Heiko Stübner [this message]
2016-03-29 1:17 ` [PATCH v6 0/3] Add more clock compatible features and support the RK3399 clock Xing Zheng
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=4649399.g7v7zsVJik@diego \
--to=heiko@sntech.de \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=elaine.zhang@rock-chips.com \
--cc=galak@codeaurora.org \
--cc=huangtao@rock-chips.com \
--cc=ijc+devicetree@hellion.org.uk \
--cc=jay.xu@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=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=sboyd@codeaurora.org \
--cc=zhengxing@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).