From: Heiko Stuebner <heiko@sntech.de>
To: Andy Yan <andy.yan@rock-chips.com>
Cc: devicetree@vger.kernel.org, linux-clk@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-rockchip@lists.infradead.org,
robh+dt@kernel.org, shawn.lin@rock-chips.com,
zhangqing@rock-chips.com, mturquette@baylibre.com,
sboyd@codeaurora.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 02/14] clk: rockchip: support more clks for rv1108
Date: Tue, 01 Aug 2017 01:31:10 +0200 [thread overview]
Message-ID: <17095133.Ri7aPbk3bA@phil> (raw)
In-Reply-To: <1501495719-21452-1-git-send-email-andy.yan@rock-chips.com>
Am Montag, 31. Juli 2017, 18:08:39 CEST schrieb Andy Yan:
> From: Elaine Zhang <zhangqing@rock-chips.com>
>
> 1. Added the description of the missing clock,
> make the clock more complete.
> 2. fix up some clk descriptions error.
>
> Signed-off-by: Elaine Zhang <zhangqing@rock-chips.com>
> Signed-off-by: Andy Yan <andy.yan@rock-chips.com>
Again, this should be split into multiple patches that are easier to review.
- pll-fixes
- fixes for existing clocks
- renames of things
- new clock-definitions
And should definitly include a bit more explanation.
Thanks
Heiko
next prev parent reply other threads:[~2017-07-31 23:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-31 10:04 [PATCH 00/14] Support more devices on rockchip rv1108 Andy Yan
2017-07-31 10:06 ` [PATCH 01/14] clk: rockchip: add more clk ids for rv1108 Andy Yan
2017-07-31 23:27 ` Heiko Stuebner
2017-07-31 10:08 ` [PATCH 02/14] clk: rockchip: support more clks " Andy Yan
2017-07-31 23:31 ` Heiko Stuebner [this message]
2017-07-31 10:10 ` [PATCH 03/14] pinctrl: rockchip: add input schmitt support " Andy Yan
2017-07-31 11:26 ` Heiko Stübner
2017-08-07 8:49 ` Linus Walleij
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=17095133.Ri7aPbk3bA@phil \
--to=heiko@sntech.de \
--cc=andy.yan@rock-chips.com \
--cc=devicetree@vger.kernel.org \
--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=robh+dt@kernel.org \
--cc=sboyd@codeaurora.org \
--cc=shawn.lin@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 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).