From: Wolfram Sang <wsa@the-dreams.de>
To: cl@rock-chips.com
Cc: heiko@sntech.de, robh+dt@kernel.org, mark.rutland@arm.com,
zhengxing@rock-chips.com, andy.yan@rock-chips.com,
jay.xu@rock-chips.com, matthias.bgg@gmail.com,
paweljarosz3691@gmail.com, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
linux-i2c@vger.kernel.org, jic23@kernel.org, knaack.h@gmx.de,
lars@metafoo.de, pmeerw@pmeerw.net, wxt@rock-chips.com,
david.wu@rock-chips.com, linux-iio@vger.kernel.org,
shawn.lin@rock-chips.com, akpm@linux-foundation.org,
dianders@chromium.org, yamada.masahiro@socionext.com,
catalin.marinas@arm.com, will.deacon@arm.com, afaerber@suse.de,
shawnguo@kernel.org, khilman@baylibre.com, arnd@arndb.de,
fabio.estevam@nxp.com, zhangqing@rock-chips.com,
kever.yang@rock-chips.com, tony.xie@rock-chips.com,
huangtao@rock-chips.com, yhx@rock-chips.com,
rocky.hao@rock-chips.com
Subject: Re: [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>
[-- Attachment #1: Type: text/plain, Size: 920 bytes --]
On Mon, Mar 27, 2017 at 05:40:45PM +0800, cl@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.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2017-03-30 15:06 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
2017-03-27 9:40 ` [PATCH v4 1/6] dt-bindings: iio: rockchip-saradc: add support for rk3328 cl
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
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
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
2017-04-04 16:15 ` Heiko Stuebner
2017-03-27 9:46 ` [PATCH v4 6/6] dt-bindings: document rockchip rk3328-evb board cl
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=afaerber@suse.de \
--cc=akpm@linux-foundation.org \
--cc=andy.yan@rock-chips.com \
--cc=arnd@arndb.de \
--cc=catalin.marinas@arm.com \
--cc=cl@rock-chips.com \
--cc=david.wu@rock-chips.com \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=fabio.estevam@nxp.com \
--cc=heiko@sntech.de \
--cc=huangtao@rock-chips.com \
--cc=jay.xu@rock-chips.com \
--cc=jic23@kernel.org \
--cc=kever.yang@rock-chips.com \
--cc=khilman@baylibre.com \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=matthias.bgg@gmail.com \
--cc=paweljarosz3691@gmail.com \
--cc=pmeerw@pmeerw.net \
--cc=robh+dt@kernel.org \
--cc=rocky.hao@rock-chips.com \
--cc=shawn.lin@rock-chips.com \
--cc=shawnguo@kernel.org \
--cc=tony.xie@rock-chips.com \
--cc=will.deacon@arm.com \
--cc=wxt@rock-chips.com \
--cc=yamada.masahiro@socionext.com \
--cc=yhx@rock-chips.com \
--cc=zhangqing@rock-chips.com \
--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).