linux-media.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sakari Ailus <sakari.ailus@iki.fi>
To: Dave Stevenson <dave.stevenson@raspberrypi.com>
Cc: paul.j.murphy@intel.com, daniele.alessandrelli@intel.com,
	linux-media@vger.kernel.org
Subject: Re: [PATCH 0/2] media: Add regulator support to ov9282
Date: Thu, 17 Nov 2022 11:40:57 +0200	[thread overview]
Message-ID: <Y3YBqQgr+Hk1H+Sy@valkosipuli.retiisi.eu> (raw)
In-Reply-To: <CAPY8ntCeh7=q2gL_4SK6jq=Mx7KfTt5YF-BkeMvv73tRGjzNPw@mail.gmail.com>

Hi Dave,

On Wed, Nov 16, 2022 at 04:50:27PM +0000, Dave Stevenson wrote:
> On Wed, 5 Oct 2022 at 16:21, Dave Stevenson
> <dave.stevenson@raspberrypi.com> wrote:
> >
> > The sensor takes 3 voltage supply rails, so add the relevant
> > configuration to the device tree bindings and driver.
> 
> A gentle ping to this patchset.
> The other patchset for ov9282 that added functionality has been merged
> and made a pull request already, and Patchwork was reporting this one
> as "Under review" for longer than that one was.
> The DT side is ack'ed, and the driver changes are pretty trivial.

Oops.

Thanks for the ping. These are in my tree now.

-- 
Kind regards,

Sakari Ailus

      reply	other threads:[~2022-11-17  9:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-05 15:20 [PATCH 0/2] media: Add regulator support to ov9282 Dave Stevenson
2022-10-05 15:20 ` [PATCH 1/2] dt-bindings: media: ovti,ov9282: Add optional regulators Dave Stevenson
2022-10-06 19:08   ` Rob Herring
2022-10-05 15:20 ` [PATCH 2/2] media: i2c: ov9282: Add support for regulators Dave Stevenson
2022-11-24  9:31   ` Alexander Stein
2022-11-24 11:58     ` Dave Stevenson
2022-11-24 12:06       ` Alexander Stein
2022-11-16 16:50 ` [PATCH 0/2] media: Add regulator support to ov9282 Dave Stevenson
2022-11-17  9:40   ` Sakari Ailus [this message]

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=Y3YBqQgr+Hk1H+Sy@valkosipuli.retiisi.eu \
    --to=sakari.ailus@iki.fi \
    --cc=daniele.alessandrelli@intel.com \
    --cc=dave.stevenson@raspberrypi.com \
    --cc=linux-media@vger.kernel.org \
    --cc=paul.j.murphy@intel.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;
as well as URLs for NNTP newsgroup(s).