From: Mauro Carvalho Chehab <mchehab@kernel.org>
To: Miles Chen <miles.chen@mediatek.com>
Cc: <lukas.bulwahn@gmail.com>, <bin.liu@mediatek.com>,
<kernel-janitors@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <linux-media@vger.kernel.org>,
<linux-mediatek@lists.infradead.org>, <matthias.bgg@gmail.com>,
Rick Chang <rick.chang@mediatek.com>
Subject: Re: [PATCH RFC] MAINTAINERS: drop unreachable contact for MEDIATEK JPEG DRIVER
Date: Fri, 13 May 2022 09:23:39 +0200 [thread overview]
Message-ID: <20220513092339.60f9eedc@coco.lan> (raw)
In-Reply-To: <20220309030431.31247-1-miles.chen@mediatek.com>
Em Wed, 9 Mar 2022 11:04:31 +0800
Miles Chen <miles.chen@mediatek.com> escreveu:
> Hi Lukas,
>
> > 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.
Funny... I did a quick test here, and the e-mail to Rick was not rejected:
Connecting to smtp.kernel.org [35.85.114.177]:587 ... TFO mode sendto, no data: EINPROGRESS
connected
SMTP<< 220 smtp.kernel.org ESMTP Postfix
SMTP>> EHLO mail.kernel.org
SMTP<< 250-smtp.kernel.org
250-PIPELINING
250-SIZE 30720000
250-VRFY
250-ETRN
250-STARTTLS
250-ENHANCEDSTATUSCODES
250-8BITMIME
250-DSN
250 CHUNKING
SMTP>> STARTTLS
SMTP<< 220 2.0.0 Ready to start TLS
SMTP>> EHLO mail.kernel.org
SMTP<< 250-smtp.kernel.org
250-PIPELINING
250-SIZE 30720000
250-VRFY
250-ETRN
250-AUTH PLAIN LOGIN
250-ENHANCEDSTATUSCODES
250-8BITMIME
250-DSN
250 CHUNKING
SMTP>> AUTH PLAIN ************************************
SMTP<< 235 2.7.0 Authentication successful
SMTP|> MAIL FROM:<mchehab@kernel.org> SIZE=1361 AUTH=mchehab@kernel.org
SMTP|> RCPT TO:<rick.chang@mediatek.com>
will write message using CHUNKING
SMTP+> BDAT 338 LAST
SMTP>> QUIT
SMTP<< 250 2.1.0 Ok
SMTP<< 250 2.1.5 Ok
SMTP<< 250 2.0.0 Ok: 338 bytes queued as 8DCF4C34100
SMTP<< 221 2.0.0 Bye
SMTP(close)>>
LOG: MAIN
=> rick.chang@mediatek.com R=smarthost T=remote_msa H=smtp.kernel.org [35.85.114.177] X=TLS1.2:ECDHE-RSA-AES256-GCM-SHA384:256 CV=yes A=client_auth_plain K C="250 2.0.0 Ok: 338 bytes queued as 8DCF4C34100"
LOG: MAIN
Completed
> >
> > Signed-off-by: Lukas Bulwahn <lukas.bulwahn@gmail.com>
>
> I confirmed that Rick Chang has left Mediatek, so it is ok to remove his name.
Ok, I'll apply the patch.
>
> Reviewed-by: Miles Chen <miles.chen@mediatek.com>
>
> Thanks,
> Miles
Thanks,
Mauro
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2022-05-13 7:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-08 11:43 [PATCH RFC] MAINTAINERS: drop unreachable contact for MEDIATEK JPEG DRIVER Lukas Bulwahn
2022-03-09 3:04 ` Miles Chen
2022-05-13 7:23 ` Mauro Carvalho Chehab [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=20220513092339.60f9eedc@coco.lan \
--to=mchehab@kernel.org \
--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=lukas.bulwahn@gmail.com \
--cc=matthias.bgg@gmail.com \
--cc=miles.chen@mediatek.com \
--cc=rick.chang@mediatek.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;
as well as URLs for NNTP newsgroup(s).