mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Bagas Sanjaya <bagasdotme@gmail.com>,
	hanyu001@208suo.com, stf_xl@wp.pl, helmut.schaa@googlemail.com,
	kvalo@kernel.org
Cc: linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] net: wireless: ralink: rt2x00: "foo* bar" should be "foo *bar"
Date: Thu, 10 Aug 2023 08:53:29 +0200	[thread overview]
Message-ID: <5fcffcebca2ef9b8c276e5f4b4464d888649a70b.camel@sipsolutions.net> (raw)
In-Reply-To: <ZNRHCBbvEPtq-cE7@debian.me>

On Thu, 2023-08-10 at 09:10 +0700, Bagas Sanjaya wrote:
> > And the email address doesn't even work, only about two weeks after you
> > sent this patch?
> > 
> >   hanyu001@208suo.com
> >     host mx1.qiye.aliyun.com [47.246.146.58]
> >     SMTP error from remote mail server after RCPT TO:<hanyu001@208suo.com>:
> >     554 RCPT (hanyu001@208suo.com) dosn't exist
> > 
> 
> No wonder why @208suo.com people ignore reviews from mailing list - their
> addresses are send-only without real mailboxes...
> 
> BTW, how can you get above error message? I'm curious.

That was just the error message I got back from my mail server,
presumably now that you actually tried emailing them, you also got one.

I'm beginning to think we should just block that whole domain until
someone there is actually willing to _interact_, not just throw
(garbage!) patches over the fence.

johannes

  reply	other threads:[~2023-08-10  6:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <tencent_316424AFC531C5F050C0203FDBA08E84F907@qq.com>
2023-07-21  6:34 ` hanyu001
2023-08-08  8:34   ` Johannes Berg
2023-08-08  8:40     ` Johannes Berg
2023-08-10  2:10       ` Bagas Sanjaya
2023-08-10  6:53         ` Johannes Berg [this message]
2023-08-10 14:18           ` Bagas Sanjaya

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=5fcffcebca2ef9b8c276e5f4b4464d888649a70b.camel@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=bagasdotme@gmail.com \
    --cc=hanyu001@208suo.com \
    --cc=helmut.schaa@googlemail.com \
    --cc=kvalo@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=stf_xl@wp.pl \
    /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

all inboxes | Powered by JetHome®