From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Quentin Schulz <foss+kernel@0leil.net>
Cc: shawnx.tu@intel.com, mchehab@kernel.org, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, linux-media@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Quentin Schulz <quentin.schulz@theobroma-systems.com>
Subject: Re: [PATCH v3 1/4] media: dt-bindings: ov5675: document YAML binding
Date: Tue, 10 May 2022 15:30:15 +0200 [thread overview]
Message-ID: <8f814e9f-2060-7361-8d36-4a34f2aece1a@linaro.org> (raw)
In-Reply-To: <20220509143226.531117-1-foss+kernel@0leil.net>
On 09/05/2022 16:32, Quentin Schulz wrote:
> From: Quentin Schulz <quentin.schulz@theobroma-systems.com>
>
> This patch adds documentation of device tree in YAML schema for the
> OV5675 CMOS image sensor from Omnivision.
>
> Signed-off-by: Quentin Schulz <quentin.schulz@theobroma-systems.com>
Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Best regards,
Krzysztof
prev parent reply other threads:[~2022-05-10 14:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-09 14:32 Quentin Schulz
2022-05-09 14:32 ` [PATCH v3 2/4] media: ov5675: add device-tree support and support runtime PM Quentin Schulz
2022-05-10 9:46 ` Jacopo Mondi
2022-05-10 13:42 ` Quentin Schulz
2022-05-25 12:24 ` Quentin Schulz
2022-05-25 12:14 ` Quentin Schulz
2022-05-09 14:32 ` [PATCH v3 3/4] media: i2c: ov5675: parse and register V4L2 device tree properties Quentin Schulz
2022-05-10 9:47 ` Jacopo Mondi
2022-05-09 14:32 ` [PATCH v3 4/4] media: i2c: ov5675: add .get_selection support Quentin Schulz
2022-05-12 9:05 ` Jacopo Mondi
2022-05-17 9:25 ` Quentin Schulz
2022-05-17 11:18 ` Jacopo Mondi
2022-05-17 12:47 ` Quentin Schulz
2022-05-20 6:31 ` Jacopo Mondi
2022-05-10 13:30 ` Krzysztof Kozlowski [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=8f814e9f-2060-7361-8d36-4a34f2aece1a@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=foss+kernel@0leil.net \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=quentin.schulz@theobroma-systems.com \
--cc=robh+dt@kernel.org \
--cc=shawnx.tu@intel.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
all inboxes | Powered by JetHome®