From: wsa@the-dreams.de (Wolfram Sang)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 0/6] initialize dtsi file and dts file for RK3328 SoCs
Date: Thu, 30 Mar 2017 17:05:57 +0200 [thread overview]
Message-ID: <20170330150557.znttalrsxpnmccx6@ninjato> (raw)
In-Reply-To: <1490607650-18650-1-git-send-email-cl@rock-chips.com>
On Mon, Mar 27, 2017 at 05:40:45PM +0800, cl at rock-chips.com wrote:
> From: Liang Chen <cl@rock-chips.com>
>
> Changes in v4:
> Remove some assigned-clocks as they should be inited in their
> respective device nodes.
>
> Changes in v3:
> Adjust some descriptions in dtsi.
>
> Changes in v2:
> Remove RK_FUNC_* in dtsi as it dose not help understand things better.
> Adjust the order of description in dt-bindings.
>
> v1:
> These patchs depend on pinctrl patchs as below:
Why didn't you renumber the patches? I and probably others wondered
where and what patch 2 is and why it could be missing. I recall now that
I applied it already. Other maintainers don't have that knowledge. Also,
since I applied your patch, no need for me or the i2c-list to be on CC.
Please no "quick fixes" when sending out patch series. I know it is
tempting but it usually creates confusion.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20170330/a5c34961/attachment.sig>
prev parent reply other threads:[~2017-03-30 15:05 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-27 9:40 [PATCH v4 0/6] initialize dtsi file and dts file for RK3328 SoCs cl at rock-chips.com
2017-03-27 9:40 ` [PATCH v4 1/6] dt-bindings: iio: rockchip-saradc: add support for rk3328 cl at rock-chips.com
2017-03-27 13:25 ` Heiko Stuebner
2017-04-02 8:58 ` Jonathan Cameron
2017-03-27 9:40 ` [PATCH v4 3/6] dt-bindings: soc: rockchip: grf: " cl at rock-chips.com
2017-04-04 15:44 ` Heiko Stuebner
2017-03-27 9:40 ` [PATCH v4 4/6] arm64: dts: rockchip: add core dtsi file for RK3328 SoCs cl at rock-chips.com
2017-03-31 8:27 ` Shawn Lin
2017-04-04 16:04 ` Heiko Stuebner
2017-04-05 2:07 ` Elaine Zhang
2017-04-05 10:11 ` Heiko Stübner
2017-03-27 9:40 ` [PATCH v4 5/6] arm64: dts: rockchip: add dts file for RK3328 cl at rock-chips.com
2017-04-04 16:15 ` Heiko Stuebner
2017-03-27 9:46 ` [PATCH v4 6/6] dt-bindings: document rockchip rk3328-evb board cl at rock-chips.com
2017-04-04 16:10 ` Heiko Stuebner
2017-03-30 15:05 ` Wolfram Sang [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=20170330150557.znttalrsxpnmccx6@ninjato \
--to=wsa@the-dreams.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox