From: Antoine Bernard <zalnir@proton.me>
To: Krzysztof Kozlowski <krzk@kernel.org>
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:52:05 +0000 [thread overview]
Message-ID: <ySoCU9RG-svsJbEsf812GyWrLdj1qAK-m_UQXD8WVeADOml0c0HrDyg3mMgxY7NVhafoUEFdXlpXZ7eqUXE1LtqUp_FOWHhwJFGPvGidskE=@proton.me> (raw)
In-Reply-To: <20260321-screeching-lovely-earwig-c0bd53@quoll>
> Do not attach (thread) your patchsets to some other threads
> (unrelated or older versions).
Sorry about that, I'll resend all patches in the series from now on.
> Looks exactly as ovti,ov08x40, no? Why another file is needed?
I kind of agree, ovti,ov08x40 looks the same. In fact, ovti,ov* documentations all look similar. I made it because after adding the dt of_match in the sensor driver, the validation script warned me that the related documentation is missing. If it is possible to have one documentation for different sensors, then I don't think this is needed.
next prev parent reply other threads:[~2026-03-21 11:52 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
2026-03-21 11:52 ` Antoine Bernard [this message]
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='ySoCU9RG-svsJbEsf812GyWrLdj1qAK-m_UQXD8WVeADOml0c0HrDyg3mMgxY7NVhafoUEFdXlpXZ7eqUXE1LtqUp_FOWHhwJFGPvGidskE=@proton.me' \
--to=zalnir@proton.me \
--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=krzk@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=~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