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 13:54:24 +0100 [thread overview]
Message-ID: <0b322851-53b3-4ff9-a632-1975c953f6d9@kernel.org> (raw)
In-Reply-To: <WAB7jp0xjjHctNtq5ASJolUOI6Kg5aMEGSDolwUfAWaAmIima-lr5dCUh-EQPBZvrUFdXMxA8dKfkY-XRkTFYhzCrp5vheC2h15to5ZsBsM=@proton.me>
On 21/03/2026 13:02, Antoine Bernard wrote:
>> Please wrap your emails.
>
> Sorry, I noticed that after sending.
>
>> If the hardware has the same properties
>
> As of my understanding they are different hardware, can I really use
> the documentation for another hardware?
I asked to document it.
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-03-21 12:54 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
2026-03-21 11:57 ` Krzysztof Kozlowski
2026-03-21 12:02 ` Antoine Bernard
2026-03-21 12:54 ` Krzysztof Kozlowski [this message]
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=0b322851-53b3-4ff9-a632-1975c953f6d9@kernel.org \
--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