From: Krzysztof Kozlowski <krzk@kernel.org>
To: Antoine Bernard <zalnir@proton.me>
Cc: Sakari Ailus <sakari.ailus@linux.intel.com>,
Arec Kao <arec.kao@intel.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>,
"linux-media@vger.kernel.org" <linux-media@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"~postmarketos/upstreaming@lists.sr.ht"
<~postmarketos/upstreaming@lists.sr.ht>
Subject: Re: [PATCH v2 2/3] media: dt-bindings: Add OmniVision OV13B10
Date: Sat, 21 Mar 2026 11:25:05 +0100 [thread overview]
Message-ID: <20260321-screeching-lovely-earwig-c0bd53@quoll> (raw)
In-Reply-To: <8or0YwK4oKEWSf5sBtuu8Xo6CYaQTVSu3BhkNBR_xv6se8zLgy4VVO3Q5gvuNk4UyQs_omqdqaqHhZBfLJuoaibc7A8foK9ISRweQCkInb8=@proton.me>
On Sat, Mar 21, 2026 at 04:36:09AM +0000, Antoine Bernard wrote:
> Document the device tree bindings for OmniVision OV13B10 image
> sensor.
>
> Signed-off-by: Antoine Bernard <zalnir@proton.me>
>
> ---
There is no 1/3 and 3/3 in this posting. There is v1 though...
Do not attach (thread) your patchsets to some other threads (unrelated
or older versions). This buries them deep in the mailbox and might
interfere with applying entire sets. See also:
https://elixir.bootlin.com/linux/v6.16-rc2/source/Documentation/process/submitting-patches.rst#L830
> v2:
> - Rename to "external clock".
> - Drop link-frequencies and remote-endpoint.
> - Set maintainer as myself.
> ---
> .../bindings/media/i2c/ovti,ov13b10.yaml | 94 +++++++++++++++++++
Looks exactly as ovti,ov08x40, no? Why another file is needed?
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-03-21 10:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-20 9:27 [PATCH 2/3] media: dt-bindings: Add OmniVision OV13B10 Antoine Bernard
2026-03-20 21:39 ` Sakari Ailus
2026-03-21 4:36 ` [PATCH v2 " Antoine Bernard
2026-03-21 10:25 ` Krzysztof Kozlowski [this message]
2026-03-21 11:52 ` Antoine Bernard
2026-03-21 11:57 ` Krzysztof Kozlowski
2026-03-21 12:02 ` Antoine Bernard
2026-03-21 12:54 ` Krzysztof Kozlowski
2026-03-20 21:40 ` [PATCH " Sakari Ailus
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=20260321-screeching-lovely-earwig-c0bd53@quoll \
--to=krzk@kernel.org \
--cc=arec.kao@intel.com \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=robh@kernel.org \
--cc=sakari.ailus@linux.intel.com \
--cc=zalnir@proton.me \
--cc=~postmarketos/upstreaming@lists.sr.ht \
/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