Linux kernel staging patches
 help / color / mirror / Atom feed
From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: Dave Stevenson <dave.stevenson@raspberrypi.com>
Cc: Dave Hansen <dave.hansen@linux.intel.com>,
	linux-kernel@vger.kernel.org, Yong Zhi <yong.zhi@intel.com>,
	Dan Scally <dan.scally@ideasonboard.com>,
	Mauro Carvalho Chehab <mchehab@kernel.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Lixu Zhang <lixu.zhang@intel.com>,
	linux-media@vger.kernel.org, linux-staging@lists.linux.dev,
	David Heidelberg <david@ixit.cz>
Subject: Re: [PATCH] MAINTAINERS: Remove bouncing Intel media maintainers
Date: Thu, 28 May 2026 22:06:34 +0300	[thread overview]
Message-ID: <ahiSOvQ2zQuHDHWI@kekkonen.localdomain> (raw)
In-Reply-To: <CAPY8ntBFG=FzJdWjU+jnjx9k5H=pSyb9AVGiYwH+Kqu2kLMLTw@mail.gmail.com>

Hi Dave,

On Thu, May 28, 2026 at 11:21:47AM +0100, Dave Stevenson wrote:
> Hi Sakari & Dave
> 
> On Wed, 27 May 2026 at 09:10, Sakari Ailus <sakari.ailus@linux.intel.com> wrote:
> >
> > Hi Dave,
> >
> > On Tue, May 26, 2026 at 02:41:31PM -0700, Dave Hansen wrote:
> > > Tianshu Qiu and Bingbu Cao are maintainers and reviewers of a bunch of
> > > media drivers (7 and 9 respectively). Both of their emails are
> > > bouncing.
> > >
> > > Remove the bouncing entries and update driver status in cases where
> > > there are no M:'s left.
> >
> > I can pick at least some of these. I'll send v2.
> 
> If Intel have no/limited interest in IMX355 any more, then I'm happy
> to step up as the maintainer as we have a customer looking to use it.
> I was going to add that as an extra patch to v2 of my recent patchset
> for it, but haven't sent it out yet.
> 
> Based on recent commits I had pinged David Heidelberg (added to cc)
> and Richard Acayan too as other potential folk with an interest. David
> has agreed to be a reviewer, but Richard hasn't the spare capacity at
> present.
> 
> I don't mind if you add that to your V2 of this set, or I'll try and
> get my v2 imx355 set out in the next week.

The sensor is present in a Chromebook and so I think there's some interest.

I'll add us both as M: and David as R: in v2.

-- 
Regards,

Sakari Ailus

      reply	other threads:[~2026-05-28 19:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-26 21:41 [PATCH] MAINTAINERS: Remove bouncing Intel media maintainers Dave Hansen
2026-05-27  8:10 ` Sakari Ailus
2026-05-28 10:21   ` Dave Stevenson
2026-05-28 19:06     ` 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=ahiSOvQ2zQuHDHWI@kekkonen.localdomain \
    --to=sakari.ailus@linux.intel.com \
    --cc=dan.scally@ideasonboard.com \
    --cc=dave.hansen@linux.intel.com \
    --cc=dave.stevenson@raspberrypi.com \
    --cc=david@ixit.cz \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    --cc=lixu.zhang@intel.com \
    --cc=mchehab@kernel.org \
    --cc=yong.zhi@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