From: Heiko Stuebner <heiko@sntech.de>
To: linux-rockchip@lists.infradead.org,
Helen Koike <helen.koike@collabora.com>,
devicetree@vger.kernel.org, linux-media@vger.kernel.org
Cc: Heiko Stuebner <heiko@sntech.de>,
jbx6244@gmail.com, robh+dt@kernel.org,
linux-kernel@vger.kernel.org, hverkuil-cisco@xs4all.nl,
mark.rutland@arm.com, devel@driverdev.osuosl.org,
ezequiel@collabora.com, kishon@ti.com, kernel@collabora.com,
karthik.poduval@gmail.com, dafna.hirschfeld@collabora.com
Subject: Re: [PATCH v2 0/9] move Rockchip ISP bindings out of staging / add ISP DT nodes for RK3399
Date: Wed, 1 Jul 2020 14:31:04 +0200 [thread overview]
Message-ID: <159360661051.89349.4172793847996909407.b4-ty@sntech.de> (raw)
In-Reply-To: <20200403161538.1375908-1-helen.koike@collabora.com>
On Fri, 3 Apr 2020 13:15:29 -0300, Helen Koike wrote:
> Move the bindings out of drivers/staging and place them in
> Documentation/devicetree/bindings instead.
>
> Also, add DT nodes for RK3399 and verify with make ARCH=arm64 dtbs_check
> and make ARCH=arm64 dt_binding_check.
>
> Tested by verifying images streamed from RockPi 4 board with imx219
> module.
>
> [...]
Applied, thanks!
[1/1] arm64: dts: rockchip: add rx0 mipi-phy for rk3399
commit: e4bfde13e323f9ee5f2f38aa5cac0676dd656f8e
Best regards,
--
Heiko Stuebner <heiko@sntech.de>
prev parent reply other threads:[~2020-07-01 12:31 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-03 16:15 [PATCH v2 0/9] move Rockchip ISP bindings out of staging / add ISP DT nodes for RK3399 Helen Koike
2020-04-03 16:15 ` [PATCH v2 1/9] media: staging: dt-bindings: rkisp1: add missing required nodes Helen Koike
2020-04-03 16:15 ` [PATCH v2 2/9] media: staging: dt-bindings: rkisp1: add required items in i2c example Helen Koike
2020-04-03 16:15 ` [PATCH v2 3/9] media: staging: dt-bindings: rkisp1: re-order properties Helen Koike
2020-04-03 16:15 ` [PATCH v2 4/9] media: staging: dt-bindings: phy-rockchip-dphy-rx0: remove non-used reg property Helen Koike
2020-04-03 16:15 ` [PATCH v2 5/9] dt-bindings: phy: phy-rockchip-dphy-rx0: move rockchip dphy rx0 bindings out of staging Helen Koike
2020-04-14 18:08 ` Rob Herring
2020-04-03 16:15 ` [PATCH v2 6/9] dt-bindings: media: rkisp1: move rockchip-isp1 " Helen Koike
2020-04-14 18:08 ` Rob Herring
2020-04-23 12:36 ` Johan Jonker
2020-04-23 13:33 ` Johan Jonker
2020-04-03 16:15 ` [PATCH v2 7/9] media: MAINTAINERS: rkisp1: add path to dt-bindings Helen Koike
2020-04-17 7:18 ` Hans Verkuil
2020-04-17 7:30 ` Joe Perches
2020-05-09 12:51 ` Ezequiel Garcia
2020-04-23 12:48 ` Johan Jonker
2020-04-03 16:15 ` [PATCH v2 8/9] arm64: dts: rockchip: add rx0 mipi-phy for rk3399 Helen Koike
2020-05-09 12:53 ` Ezequiel Garcia
2020-04-03 16:15 ` [PATCH v2 9/9] arm64: dts: rockchip: add isp0 node " Helen Koike
2020-07-01 12:31 ` Heiko Stuebner [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=159360661051.89349.4172793847996909407.b4-ty@sntech.de \
--to=heiko@sntech.de \
--cc=dafna.hirschfeld@collabora.com \
--cc=devel@driverdev.osuosl.org \
--cc=devicetree@vger.kernel.org \
--cc=ezequiel@collabora.com \
--cc=helen.koike@collabora.com \
--cc=hverkuil-cisco@xs4all.nl \
--cc=jbx6244@gmail.com \
--cc=karthik.poduval@gmail.com \
--cc=kernel@collabora.com \
--cc=kishon@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.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;
as well as URLs for NNTP newsgroup(s).