From: Matthew Wilcox <willy@infradead.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: hexingwei001@208suo.com, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm: page_io: Prefer 'unsigned int' to bare use of 'unsigned'
Date: Wed, 14 Jun 2023 19:12:58 +0100 [thread overview]
Message-ID: <ZIoDKqBt2uNSbblB@casper.infradead.org> (raw)
In-Reply-To: <20230614110923.b5ac015ac6e9a2d97f3b40c3@linux-foundation.org>
On Wed, Jun 14, 2023 at 11:09:23AM -0700, Andrew Morton wrote:
> On Wed, 14 Jun 2023 15:23:44 +0800 hexingwei001@208suo.com wrote:
All the patches from 208suo.com should be discarded. From conversations
I've seen elsewhere, they aren't compile tested, they're whitespace
damaged and often they're just wrong.
<x> has anyone seen 208suo.com patches?
<x> so far all I've seen are either utterly wrong or won't even compile
<x> and a bunch of different email addresses/names from that domain, but all the patches coming at around the same time? it's very weird
<x> and also all the same kind of patches
<x> "remove unneeded variable" - per coccicheck, which is just not smart enough about the macro constructions
<x> and of course 20 minutes after I ask them to stop, they send another broken patch
prev parent reply other threads:[~2023-06-14 18:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230614071804.13110-1-panzhiai@cdjrlc.com>
[not found] ` <1e132a6416d673e285af610ff185fa5f@208suo.com>
2023-06-14 8:41 ` David Hildenbrand
2023-06-14 18:09 ` Andrew Morton
2023-06-14 18:12 ` Matthew Wilcox [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=ZIoDKqBt2uNSbblB@casper.infradead.org \
--to=willy@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=hexingwei001@208suo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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