From: Kalle Valo <kvalo@kernel.org>
To: hanyu001@208suo.com
Cc: stf_xl@wp.pl, helmut.schaa@googlemail.com,
linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] wireless: ralink: rt2x00: Remove unnecessary spaces
Date: Fri, 21 Jul 2023 13:45:50 +0300 [thread overview]
Message-ID: <87pm4l35lt.fsf@kernel.org> (raw)
In-Reply-To: <c0f897b57f6b05d26f2c006154fa15ed@208suo.com> (hanyu's message of "Fri, 21 Jul 2023 17:37:59 +0800")
hanyu001@208suo.com writes:
> Fix checkpatch warnings:
>
> ./drivers/net/wireless/ralink/rt2x00/rt2x00reg.h:168: ERROR: space
> prohibited after that open parenthesis '('
> ./drivers/net/wireless/ralink/rt2x00/rt2x00reg.h:168: ERROR: space
> prohibited before that close parenthesis ')'
> ./drivers/net/wireless/ralink/rt2x00/rt2x00reg.h:169: ERROR: space
> prohibited after that open parenthesis '('
> ./drivers/net/wireless/ralink/rt2x00/rt2x00reg.h:169: ERROR: space
> prohibited before that close parenthesis ')'
>
> Signed-off-by: Yu Han <hanyu001@208suo.com>
I have seen a lot of checkpatch fixes from you. We do not really like
random checkpatch fixes from new people, too much work for very little
gain. From looking at the title it's clear that you have not even read
our wireless specific instructions from our wiki (see link below).
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
prev parent reply other threads:[~2023-07-21 10:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <tencent_0AFA418AB6A31D66F3B0481E8BC58A70A108@qq.com>
2023-07-21 9:37 ` [PATCH] wireless: ralink: rt2x00: Remove unnecessary spaces hanyu001
2023-07-21 10:45 ` Kalle Valo [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=87pm4l35lt.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=hanyu001@208suo.com \
--cc=helmut.schaa@googlemail.com \
--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;
as well as URLs for NNTP newsgroup(s).