From: Kieran Bingham <kieran.bingham@ideasonboard.com>
To: Hans Verkuil <hverkuil@xs4all.nl>,
Helen Fornazier <helen.fornazier@gmail.com>,
Sebastian Fricke <sebastian.fricke@posteo.net>,
Shuah Khan <skhan@linuxfoundation.org>
Cc: dafna@fastmail.com,
Benjamin Gaignard <benjamin.gaignard@collabora.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
Nicolas Dufresne <nicolas.dufresne@collabora.com>,
linux-media@vger.kernel.org,
Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: Deprecated Maintainer entries?
Date: Tue, 22 Feb 2022 19:59:59 +0000 [thread overview]
Message-ID: <164555999952.3548538.14050135200074246530@Monstersaurus> (raw)
In-Reply-To: <ac23b61c-10c8-a36c-6da8-d232b8399503@linuxfoundation.org>
Quoting Shuah Khan (2022-02-22 15:17:01)
> Hi Hans,
>
> On 2/22/22 12:46 AM, Hans Verkuil wrote:
> > The same is true for VIMC where Helen was maintainer. Shuah, would you
> > be willing to take over VIMC as maintainer? If not, then I can put myself
> > up there as maintainer (but 'odd fixes' only, probably).
> >
>
> I will be happy to take over VIMC as maintainer.
>
> Keiran, you said you can help - would you like to be a reviewer? Let
> me know the role you would like to play. I will send patch to update
> the MAINTAINER entry for the driver.
Sure, please add kieran.bingham@ideasonboard.com.
Thanks
--
Kieran
>
> Helen, sorry to see you leave the community. Hope you will be able to
> come back in the future.
>
> thanks,
> -- Shuah
prev parent reply other threads:[~2022-02-22 20:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-22 6:32 Deprecated Maintainer entries? Sebastian Fricke
2022-02-22 7:46 ` Hans Verkuil
2022-02-22 9:33 ` Kieran Bingham
2022-02-22 13:23 ` Helen Mae Koike Fornazier
2022-02-22 15:17 ` Shuah Khan
2022-02-22 19:59 ` Kieran Bingham [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=164555999952.3548538.14050135200074246530@Monstersaurus \
--to=kieran.bingham@ideasonboard.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=benjamin.gaignard@collabora.com \
--cc=dafna@fastmail.com \
--cc=helen.fornazier@gmail.com \
--cc=hverkuil@xs4all.nl \
--cc=linux-media@vger.kernel.org \
--cc=nicolas.dufresne@collabora.com \
--cc=sebastian.fricke@posteo.net \
--cc=skhan@linuxfoundation.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;
as well as URLs for NNTP newsgroup(s).