From: Bryan O'Donoghue <bod@kernel.org>
To: Wenmeng Liu <wenmeng.liu@oss.qualcomm.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Sakari Ailus <sakari.ailus@linux.intel.com>,
Vladimir Zapolskiy <vladimir.zapolskiy@linaro.org>
Cc: linux-media@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/3] media: i2c: og0ve1b: Introduce per-sensor data structure
Date: Mon, 6 Jul 2026 14:47:09 +0100 [thread overview]
Message-ID: <ff3dc3a7-2d1a-4065-b197-03e8112ccdd1@kernel.org> (raw)
In-Reply-To: <b518fb22-b4db-464b-9318-43cc9663ef4c@oss.qualcomm.com>
On 06/07/2026 14:36, Wenmeng Liu wrote:
>>> + return 0;
>> The one thing that is not immediately clear to me is if we get
>> equivalent logic WRT OG0VE1B_REG_PRE_ISP after this change.
>>
> I will kill OG0VE1B_REG_PRE_ISP logic in next version.
Kill, steady on.
Just double check and be sure about it, is all I mean.
---
bod
next prev parent reply other threads:[~2026-07-06 13:47 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-02 10:52 [PATCH v2 0/3] media: i2c: Add OmniVision OG0VA1B camera sensor driver Wenmeng Liu
2026-07-02 10:52 ` [PATCH v2 1/3] dt-bindings: media: i2c: og0ve1b: Add OmniVision OG0VA1B camera sensor Wenmeng Liu
2026-07-02 12:24 ` Vladimir Zapolskiy
2026-07-06 13:31 ` Wenmeng Liu
2026-07-02 19:21 ` Conor Dooley
2026-07-02 10:52 ` [PATCH v2 2/3] media: i2c: og0ve1b: Introduce per-sensor data structure Wenmeng Liu
2026-07-02 11:04 ` sashiko-bot
2026-07-02 13:10 ` Vladimir Zapolskiy
2026-07-06 13:34 ` Wenmeng Liu
2026-07-02 16:31 ` Bryan O'Donoghue
2026-07-06 13:36 ` Wenmeng Liu
2026-07-06 13:47 ` Bryan O'Donoghue [this message]
2026-07-02 10:52 ` [PATCH v2 3/3] media: i2c: og0ve1b: Add support for OmniVision OG0VA1B Wenmeng Liu
2026-07-02 13:16 ` Vladimir Zapolskiy
2026-07-06 13:35 ` Wenmeng Liu
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=ff3dc3a7-2d1a-4065-b197-03e8112ccdd1@kernel.org \
--to=bod@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--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=vladimir.zapolskiy@linaro.org \
--cc=wenmeng.liu@oss.qualcomm.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