From: Marek Szyprowski <m.szyprowski@samsung.com>
To: Tomasz Figa <tfiga@chromium.org>, linux-media@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, "Hans Verkuil" <hverkuil@xs4all.nl>,
"Mauro Carvalho Chehab" <mchehab@kernel.org>,
"Paweł Ościak" <posciak@chromium.org>,
"Pawel Osciak" <pawel@osciak.com>,
"Kyungmin Park" <kyungmin.park@samsung.com>
Subject: Re: [PATCH] MAINTAINERS: media: Add Tomasz Figa as a videobuf2 reviewer
Date: Tue, 11 Jun 2019 12:00:11 +0200 [thread overview]
Message-ID: <4acd9745-216b-8cd4-9f6f-bbfc870a6c0d@samsung.com> (raw)
In-Reply-To: <20190607083518.90078-1-tfiga@chromium.org>
On 2019-06-07 10:35, Tomasz Figa wrote:
> I tend to review most of the vb2 patches anyway and we need some active
> reviewers, so let add me to the MAINTAINERS file as such.
>
> Signed-off-by: Tomasz Figa <tfiga@chromium.org>
Acked-by: Marek Szyprowski <m.szyprowski@samsung.com>
> ---
> MAINTAINERS | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 98cd84977350..b5f65f61becb 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -16758,6 +16758,7 @@ VIDEOBUF2 FRAMEWORK
> M: Pawel Osciak <pawel@osciak.com>
> M: Marek Szyprowski <m.szyprowski@samsung.com>
> M: Kyungmin Park <kyungmin.park@samsung.com>
> +R: Tomasz Figa <tfiga@chromium.org>
> L: linux-media@vger.kernel.org
> S: Maintained
> F: drivers/media/common/videobuf2/*
Best regards
--
Marek Szyprowski, PhD
Samsung R&D Institute Poland
prev parent reply other threads:[~2019-06-11 10:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20190607083531epcas3p48cf46e033280d7e86ed1029707f2f373@epcas3p4.samsung.com>
2019-06-07 8:35 ` [PATCH] MAINTAINERS: media: Add Tomasz Figa as a videobuf2 reviewer Tomasz Figa
2019-06-11 10:00 ` Marek Szyprowski [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=4acd9745-216b-8cd4-9f6f-bbfc870a6c0d@samsung.com \
--to=m.szyprowski@samsung.com \
--cc=hverkuil@xs4all.nl \
--cc=kyungmin.park@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=pawel@osciak.com \
--cc=posciak@chromium.org \
--cc=tfiga@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).