linux-kernel - Re: [PATCH] media: dt-bindings: Add OmniVision OV02C10

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <21393e75-d9a2-4410-9616-b1bd6af7a7d8@linaro.org>
Date: Thu, 27 Mar 2025 16:06:23 +0000
From: Bryan O'Donoghue <bryan.odonoghue@...aro.org>
To: Bryan O'Donoghue <bod@...nel.org>, Krzysztof Kozlowski <krzk@...nel.org>,
 robh@...nel.org, hdegoede@...hat.com, mchehab@...nel.org,
 krzk+dt@...nel.org, conor+dt@...nel.org, sakari.ailus@...ux.intel.com,
 hverkuil@...all.nl
Cc: linux-media@...r.kernel.org, devicetree@...r.kernel.org,
 linux-kernel@...r.kernel.org
Subject: Re: [PATCH] media: dt-bindings: Add OmniVision OV02C10

On 27/03/2025 15:07, Bryan O'Donoghue wrote:
> On 27/03/2025 07:09, Krzysztof Kozlowski wrote:
>> On 26/03/2025 18:34, Bryan O'Donoghue wrote:
>>>>
>>>> I meant bindings are exactly the same, unless I missed something.
>>>> Devices are similar enough as well.
>>>>
>>>>> Seems simpler to me to have two separate files ?
>>>>
>>>> Not really, more files to maintain, more trivialities to fix if we
>>>> decide to change something in all bindings (e.g. style).
>>>>
>>>> Best regards,
>>>> Krzysztof
>>>
>>> Hmm, so we have two in-flight series and one yaml file.
>>>
>>> OK, I'll drop this patch and add ov02c10 to the ov02e10 yaml as you 
>>> suggest.
>>>
>>> So long as the yaml file goes in first, the order of application of the
>>> ov02c10/ov02e10 drivers won't matter and can be fixed with a cherry- 
>>> pick.
>> You can combine the series or add here a dependency.
>>
>> Best regards,
>> Krzysztof
> 
> So just in terms of sequencing, are you happy for us to merge ovo2c10 
> and then do ov02e10 ?
> 
> Since I have a bunch of driver work to do on ov02e10 I think this would 
> make sense.
> 
> ---
> bod

Just to be clear I mean merge this yaml with ov02c10, then adding ov02e 
to that yaml later on.

I'd expect there is 1-3 more submission cycles on the ov02e side.

---
bod