From: Tomasz Figa <tfiga@chromium.org>
To: linux-media@vger.kernel.org
Cc: "Mauro Carvalho hehab" <mchehab+huawei@kernel.org>,
linux-kernel@vger.kernel.org, "Hans Verkuil" <hverkuil@xs4all.nl>,
"Paweł Ościak" <posciak@chromium.org>,
"Kyungmin Park" <kyungmin.park@samsung.com>,
"Marek Szyprowski" <m.szyprowski@samsung.com>,
"Pawel Osciak" <pawel@osciak.com>,
"Tomasz Figa" <tfiga@chromium.org>
Subject: [PATCH 0/3] Clean the videobuf2 maintainer list
Date: Thu, 20 Aug 2020 12:58:22 +0000 [thread overview]
Message-ID: <20200820125825.224788-1-tfiga@chromium.org> (raw)
Currently the MAINTAINERS file lists 3 maintainers and 1 reviewer for
the VIDEOBUF2 FRAMEWORK entry. From the list, two people have been
inactive for several years. This series tries to clean the list to
ensure that the framework has only active maintainers.
The series proposes removing Kyungmin Park and Pawel Osciak from the
maintainers list. I know both of the people in person and am well aware
of their achievements for the framework in the past. However, the
framework needs to move forward and thus, it needs active maintainers.
Therefore, I'd like the people in question to comment on their plans
regarding the maintenance of this framework or lack of thereof (and thus
being fine with the removal).
Tomasz Figa (3):
MAINTAINERS: Make Tomasz the main maintainer of videobuf2
MAINTAINERS: Remove Kyungmin from the maintainers list of videobuf2
MAINTAINERS: Remove Pawel from the maintainers list of videobuf2
MAINTAINERS | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
--
2.28.0.220.ged08abb693-goog
next reply other threads:[~2020-08-20 12:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-20 12:58 Tomasz Figa [this message]
2020-08-20 12:58 ` [PATCH 1/3] MAINTAINERS: Make Tomasz the main maintainer of videobuf2 Tomasz Figa
2020-08-20 12:58 ` [PATCH 2/3] MAINTAINERS: Remove Kyungmin from the maintainers list " Tomasz Figa
2020-08-20 12:58 ` [PATCH 3/3] MAINTAINERS: Remove Pawel " Tomasz Figa
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=20200820125825.224788-1-tfiga@chromium.org \
--to=tfiga@chromium.org \
--cc=hverkuil@xs4all.nl \
--cc=kyungmin.park@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=mchehab+huawei@kernel.org \
--cc=pawel@osciak.com \
--cc=posciak@chromium.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).