From: Matthew Wilcox <willy@infradead.org>
To: chenguohua@jari.cn
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] xarray: Clean up errors in xarray.h
Date: Wed, 27 Sep 2023 07:55:24 +0100 [thread overview]
Message-ID: <ZRPR3NZVA6a1rlFz@casper.infradead.org> (raw)
In-Reply-To: <4f35bcee.861.18ad5449079.Coremail.chenguohua@jari.cn>
On Wed, Sep 27, 2023 at 02:12:35PM +0800, chenguohua@jari.cn wrote:
> Fix the following errors reported by checkpatch:
>
> ERROR: "foo * bar" should be "foo *bar"
Checkpatch is wrong. It's just a stupid script. Can't you use your
brain to look at the code you're changing and understand why it's laid
out like that?
next prev parent reply other threads:[~2023-09-27 6:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-27 6:12 [PATCH] xarray: Clean up errors in xarray.h chenguohua
2023-09-27 6:55 ` Matthew Wilcox [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-09-27 6:07 chenguohua
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=ZRPR3NZVA6a1rlFz@casper.infradead.org \
--to=willy@infradead.org \
--cc=chenguohua@jari.cn \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.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).