From: Lukas Bulwahn <lukas.bulwahn@gmail.com>
To: Bin Liu <bin.liu@mediatek.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
linux-media@vger.kernel.org,
Matthias Brugger <matthias.bgg@gmail.com>
Cc: linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org,
kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org,
Lukas Bulwahn <lukas.bulwahn@gmail.com>
Subject: [PATCH RFC] MAINTAINERS: drop unreachable contact for MEDIATEK JPEG DRIVER
Date: Tue, 8 Mar 2022 12:43:00 +0100 [thread overview]
Message-ID: <20220308114300.12502-1-lukas.bulwahn@gmail.com> (raw)
After sending a patch to Rick Chang, the mediatek mail server responded:
** Message not delivered **
Your message couldn't be delivered to rick.chang@mediatek.com because
the remote server is misconfigured. See technical details below for more
information.
The response from the remote server was:
550 Relaying mail to rick.chang@mediatek.com is not allowed
So, drop Rick Chang from the MEDIATEK JPEG DRIVER section.
Signed-off-by: Lukas Bulwahn <lukas.bulwahn@gmail.com>
---
If Rick Chang is gone, pick this patch.
MAINTAINERS | 1 -
1 file changed, 1 deletion(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index 8c7e40e1215e..02a75dd04187 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -12334,7 +12334,6 @@ F: drivers/iommu/mtk_iommu*
F: include/dt-bindings/memory/mt*-port.h
MEDIATEK JPEG DRIVER
-M: Rick Chang <rick.chang@mediatek.com>
M: Bin Liu <bin.liu@mediatek.com>
S: Supported
F: Documentation/devicetree/bindings/media/mediatek-jpeg-*.yaml
--
2.17.1
next reply other threads:[~2022-03-08 11:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-08 11:43 Lukas Bulwahn [this message]
2022-03-09 3:04 ` [PATCH RFC] MAINTAINERS: drop unreachable contact for MEDIATEK JPEG DRIVER Miles Chen
2022-05-13 7:23 ` Mauro Carvalho Chehab
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=20220308114300.12502-1-lukas.bulwahn@gmail.com \
--to=lukas.bulwahn@gmail.com \
--cc=bin.liu@mediatek.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=mchehab@kernel.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).