public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: Arun T <arun.t@intel.com>
Cc: johannes.goede@oss.qualcomm.com, arec.kao@intel.com,
	ilpo.jarvinen@linux.intel.com, dan.scally@ideasonboard.com,
	platform-driver-x86@vger.kernel.org, linux-media@vger.kernel.org,
	linux-kernel@vger.kernel.org, mehdi.djait@intel.com
Subject: Re: [PATCH v7 2/2] media: ov13b10: Support multiple regulators
Date: Wed, 1 Apr 2026 15:40:56 +0300	[thread overview]
Message-ID: <ac0SWIPXv6SQo2zy@kekkonen.localdomain> (raw)
In-Reply-To: <20260401122030.3955499-3-arun.t@intel.com>

Hi Arun,

On Wed, Apr 01, 2026 at 05:50:30PM +0530, Arun T wrote:
> The OV13B10 sensor driver currently handles a single regulator called
> avdd, however the sensor can be supplied by up to three regulators.
> Update the driver to handle all of them together using the regulator
> bulk API.
> 
> Signed-off-by: Arun T <arun.t@intel.com>
> Reviewed-by: Daniel Scally <dan.scally@ideasonboard.com>
> Reviewed-by: Sakari Ailus <sakari.ailus@linux.intel.com>

You can't add Reviewed-by: tags that haven't been explicitly (or otherwise)
given. I haven't given mine on either of the two patches, for instance.

What about the other two?

> Reviewed-by: Hans de Goede <johannes.goede@oss.qualcomm.com

-- 
Regards,

Sakari Ailus

  reply	other threads:[~2026-04-02  6:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-01 12:20 [PATCH v7 0/2] Add TPS68470 power supply support for ov13b10 sensor Arun T
2026-04-01 12:20 ` [PATCH v7 1/2] platform/x86: int3472: Add TPS68470 board data for Intel nvl Arun T
2026-04-01 12:20 ` [PATCH v7 2/2] media: ov13b10: Support multiple regulators Arun T
2026-04-01 12:40   ` Sakari Ailus [this message]
2026-04-02  7:35     ` T, Arun
2026-04-02 10:26       ` Ilpo Järvinen

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=ac0SWIPXv6SQo2zy@kekkonen.localdomain \
    --to=sakari.ailus@linux.intel.com \
    --cc=arec.kao@intel.com \
    --cc=arun.t@intel.com \
    --cc=dan.scally@ideasonboard.com \
    --cc=ilpo.jarvinen@linux.intel.com \
    --cc=johannes.goede@oss.qualcomm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mehdi.djait@intel.com \
    --cc=platform-driver-x86@vger.kernel.org \
    /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