From: Johannes Berg <johannes@sipsolutions.net>
To: 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: Tue, 08 Aug 2023 10:40:53 +0200 [thread overview]
Message-ID: <bed853f70773496902b5676e568922edbf487dfb.camel@sipsolutions.net> (raw)
In-Reply-To: <36e36d94e81da4342283aac471fb5a7bd3eb9f65.camel@sipsolutions.net>
On Tue, 2023-08-08 at 10:34 +0200, Johannes Berg wrote:
> On Fri, 2023-07-21 at 14:34 +0800, hanyu001@208suo.com wrote:
> > Fix checkpatch warnings:
> >
> > ./drivers/net/wireless/ralink/rt2x00/rt2x00.h:386: ERROR: "foo* bar"
> > should be "foo *bar"
> > ./drivers/net/wireless/ralink/rt2x00/rt2x00.h:513: ERROR: "foo* bar"
> > should be "foo *bar"
> >
> > Signed-off-by: Yu Han <hanyu001@208suo.com>
>
> This patch is broken. I'll just point you to what I wrote before:
>
> https://lore.kernel.org/all/058dd31ef48495f8641f5b66839aaea039af0f08.camel@sipsolutions.net/
>
> What _are_ you trying to achieve?!
>
> Currently all you're achieving is annoying everyone with broken (and
> pointless submissions).
>
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
johannes
next prev parent reply other threads:[~2023-08-08 21:58 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 [this message]
2023-08-10 2:10 ` Bagas Sanjaya
2023-08-10 6:53 ` Johannes Berg
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=bed853f70773496902b5676e568922edbf487dfb.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--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®