From: Conor Dooley <conor@kernel.org>
To: Jacopo Mondi <jacopo.mondi@ideasonboard.com>
Cc: Sakari Ailus <sakari.ailus@linux.intel.com>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-media@vger.kernel.org,
Kieran Bingham <kieran.bingham@ideasonboard.com>,
devicetree@vger.kernel.org, Lee Jackson <lee.jackson@arducam.com>
Subject: Re: [PATCH 1/2] media: dt-bindings: Add OmniVision OV64A40
Date: Wed, 11 Oct 2023 16:53:34 +0100 [thread overview]
Message-ID: <20231011-conflict-monument-75379ef495cc@spud> (raw)
In-Reply-To: <20231010151208.29564-2-jacopo.mondi@ideasonboard.com>
[-- Attachment #1: Type: text/plain, Size: 1040 bytes --]
Hey,
On Tue, Oct 10, 2023 at 05:12:07PM +0200, Jacopo Mondi wrote:
> Add bindings for OmniVision OV64A40.
>
> Signed-off-by: Jacopo Mondi <jacopo.mondi@ideasonboard.com>
> Signed-off-by: Lee Jackson <lee.jackson@arducam.com>
What does Lee's SoB indicate here?
> diff --git a/MAINTAINERS b/MAINTAINERS
> index b19995690904..df089d68b58c 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -15821,6 +15821,13 @@ S: Maintained
> T: git git://linuxtv.org/media_tree.git
> F: drivers/media/i2c/ov5695.c
>
> +OMNIVISION OV64A40 SENSOR DRIVER
> +M: Jacopo Mondi <jacopo.mondi@ideasonboard.org>
> +L: linux-media@vger.kernel.org
> +S: Maintained
> +T: git git://linuxtv.org/media_tree.git
Binding looks fine to me, my question is here. Usually having a tree
here means that you apply the patches yourself. Do you?
Cheers,
Conor.
> +F: Documentation/devicetree/bindings/media/i2c/ovti,ov64a40.yaml
> +
> OMNIVISION OV7670 SENSOR DRIVER
> L: linux-media@vger.kernel.org
> S: Orphan
> --
> 2.42.0
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2023-10-11 15:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20231010151208.29564-1-jacopo.mondi@ideasonboard.com>
2023-10-10 15:12 ` [PATCH 1/2] media: dt-bindings: Add OmniVision OV64A40 Jacopo Mondi
2023-10-11 15:53 ` Conor Dooley [this message]
2023-10-11 16:12 ` Jacopo Mondi
2023-10-11 16:16 ` Conor Dooley
2023-10-11 16:24 ` Laurent Pinchart
2023-10-12 15:33 ` Conor Dooley
2023-10-12 15:37 ` Rob Herring
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=20231011-conflict-monument-75379ef495cc@spud \
--to=conor@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jacopo.mondi@ideasonboard.com \
--cc=kieran.bingham@ideasonboard.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=lee.jackson@arducam.com \
--cc=linux-media@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=sakari.ailus@linux.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;
as well as URLs for NNTP newsgroup(s).