From: Heiko Stuebner <heiko@sntech.de>
To: Brian Norris <briannorris@chromium.org>
Cc: Archit Taneja <architt@codeaurora.org>,
Andrzej Hajda <a.hajda@samsung.com>,
Laurent Pinchart <Laurent.pinchart@ideasonboard.com>,
David Airlie <airlied@linux.ie>,
Yannick Fertre <yannick.fertre@st.com>,
Philippe Cornu <philippe.cornu@st.com>,
Benjamin Gaignard <benjamin.gaignard@linaro.org>,
Vincent Abriou <vincent.abriou@st.com>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
Sean Paul <seanpaul@chromium.org>,
Nickey Yang <nickey.yang@rock-chips.com>,
hl@rock-chips.com, linux-rockchip@lists.infradead.org,
mka@chromium.org, Doug Anderson <dianders@chromium.org>,
robh+dt@kernel.org, mark.rutland@arm.com, hoegsberg@gmail.com,
zyw@rock-chips.com, xbl@rock-chips.com
Subject: Re: [PATCH v4] arm64: dts: rockchip: update mipi cells for RK3399
Date: Mon, 04 Dec 2017 11:05:56 +0100 [thread overview]
Message-ID: <1731157.IgmvaAa2Kc@phil> (raw)
In-Reply-To: <20171129184755.77187-1-briannorris@chromium.org>
Am Mittwoch, 29. November 2017, 10:47:55 CET schrieb Brian Norris:
> From: Nickey Yang <nickey.yang@rock-chips.com>
>
> We might include additional ports in derivative device trees, so the
> 'port' node should have an address, and the parent 'ports' node needs
> /#{addres,size}-cells.
>
> v4:
> * keep #{address,size}-cells in both 'ports' and 'port@0' nodes
> * separate from the rest of the series, since this is mostly
> independent of the driver refactoring
>
> Signed-off-by: Nickey Yang <nickey.yang@rock-chips.com>
> Signed-off-by: Brian Norris <briannorris@chromium.org>
applied for 4.16 with Doug's Review
Thanks
Heiko
next prev parent reply other threads:[~2017-12-04 10:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-29 18:47 [PATCH v4] arm64: dts: rockchip: update mipi cells for RK3399 Brian Norris
2017-11-29 20:52 ` Doug Anderson
2017-12-04 10:05 ` Heiko Stuebner [this message]
2017-12-04 13:22 ` Laurent Pinchart
2017-12-04 13:46 ` Heiko Stuebner
2017-12-04 16:36 ` Laurent Pinchart
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=1731157.IgmvaAa2Kc@phil \
--to=heiko@sntech.de \
--cc=Laurent.pinchart@ideasonboard.com \
--cc=a.hajda@samsung.com \
--cc=airlied@linux.ie \
--cc=architt@codeaurora.org \
--cc=benjamin.gaignard@linaro.org \
--cc=briannorris@chromium.org \
--cc=dianders@chromium.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=hl@rock-chips.com \
--cc=hoegsberg@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=mka@chromium.org \
--cc=nickey.yang@rock-chips.com \
--cc=philippe.cornu@st.com \
--cc=robh+dt@kernel.org \
--cc=seanpaul@chromium.org \
--cc=vincent.abriou@st.com \
--cc=xbl@rock-chips.com \
--cc=yannick.fertre@st.com \
--cc=zyw@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