From: Rob Herring <robh@kernel.org>
To: Shunqian Zheng <zhengsq@rock-chips.com>
Cc: mchehab@kernel.org, mark.rutland@arm.com,
linux-media@vger.kernel.org, devicetree@vger.kernel.org,
ddl@rock-chips.com, tfiga@chromium.org
Subject: Re: [PATCH v6 1/4] dt-bindings: media: Add bindings for OV5695
Date: Fri, 19 Jan 2018 18:32:18 -0600 [thread overview]
Message-ID: <20180120003218.rstk2bwqh43vaxfi@rob-hp-laptop> (raw)
In-Reply-To: <1516094521-22708-2-git-send-email-zhengsq@rock-chips.com>
On Tue, Jan 16, 2018 at 05:21:58PM +0800, Shunqian Zheng wrote:
> Add device tree binding documentation for the OV5695 sensor.
>
> Signed-off-by: Shunqian Zheng <zhengsq@rock-chips.com>
> Reviewed-by: Jacopo Mondi <jacopo+renesas@jmondi.org>
> ---
> .../devicetree/bindings/media/i2c/ov5695.txt | 41 ++++++++++++++++++++++
> 1 file changed, 41 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/media/i2c/ov5695.txt
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2018-01-20 0:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-16 9:21 [PATCH v6 0/4] Add supports for OV2685 and OV5695 sensors Shunqian Zheng
2018-01-16 9:21 ` [PATCH v6 1/4] dt-bindings: media: Add bindings for OV5695 Shunqian Zheng
2018-01-20 0:32 ` Rob Herring [this message]
2018-01-16 9:21 ` [PATCH v6 2/4] media: ov5695: add support for OV5695 sensor Shunqian Zheng
2018-01-16 9:22 ` [PATCH v6 3/4] dt-bindings: media: Add bindings for OV2685 Shunqian Zheng
2018-01-20 0:33 ` Rob Herring
[not found] ` <1516094521-22708-1-git-send-email-zhengsq-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2018-01-16 9:22 ` [PATCH v6 4/4] media: ov2685: add support for OV2685 sensor Shunqian Zheng
[not found] ` <1516094521-22708-5-git-send-email-zhengsq-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2018-01-18 22:48 ` Sakari Ailus
2018-01-19 7:47 ` Shunqian Zheng
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=20180120003218.rstk2bwqh43vaxfi@rob-hp-laptop \
--to=robh@kernel.org \
--cc=ddl@rock-chips.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mchehab@kernel.org \
--cc=tfiga@chromium.org \
--cc=zhengsq@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).