From: Damien Le Moal <dlemoal@kernel.org>
To: hanyu001@208suo.com
Cc: linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ata: remove whitespace after '(' and before ')'
Date: Tue, 18 Jul 2023 19:46:02 +0900 [thread overview]
Message-ID: <da716584-253b-8c8e-ff28-7ba207d0bd7d@kernel.org> (raw)
In-Reply-To: <07f7ac9c59d027f959a69836fee9940c@208suo.com>
On 7/18/23 17:53, hanyu001@208suo.com wrote:
> This patch fixes the following checkpatch errors:
The subject should be:
ata: pata_sis: xxx
But in any case, the above message says that this is a warning from checkpatch.
But what are you patching to get this ? If you run checkpatch directly on
drivers/ata/pata_sis.c, you will get *a lot* more warnings than just this. And I
would not want patches to fix that, unless the warnings are also generated with
"make W=1" or "make C=1".
If you actually fix a bug in this driver that touches code around the lines you
touch, then it is fine to fix that to avoid the warnings, but not just for the
sake of it. libata code overall has a lot of code style issues that will trigger
checkpatch warnings. When code is changed, fixing the code style at the same
time is fine.
Exception to this is again if you see warnings with "make W=1" or "make C=1". I
applied a lot of patches recently to fix the code style in the pata_parport
protocol modules because they were generating compilation warnings.
>
> ./drivers/ata/pata_sis.c:691: ERROR: space prohibited after that open
> parenthesis '('
> ./drivers/ata/pata_sis.c:691: ERROR: space prohibited before that close
> parenthesis ')'
>
> Signed-off-by: Yu Han < hanyu001@208suo.com>
> ---
> drivers/ata/pata_sis.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/ata/pata_sis.c b/drivers/ata/pata_sis.c
> index 31de06b..2019777 100644
> --- a/drivers/ata/pata_sis.c
> +++ b/drivers/ata/pata_sis.c
> @@ -688,7 +688,7 @@ static void sis_fixup(struct pci_dev *pdev, struct
> sis_chipset *sis)
>
> if (sis->info == &sis_info33) {
> pci_read_config_byte(pdev, PCI_CLASS_PROG, ®);
> - if (( reg & 0x0F ) != 0x00)
> + if ((reg & 0x0F) != 0x00)
> pci_write_config_byte(pdev, PCI_CLASS_PROG, reg & 0xF0);
> /* Fall through to ATA16 fixup below */
> }
--
Damien Le Moal
Western Digital Research
prev parent reply other threads:[~2023-07-18 10:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <tencent_6714ED434F83826DD33A8EE7B99064165309@qq.com>
2023-07-18 8:53 ` hanyu001
2023-07-18 9:12 ` Sergei Shtylyov
2023-07-18 9:44 ` Sergey Shtylyov
2023-07-18 10:46 ` Damien Le Moal [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=da716584-253b-8c8e-ff28-7ba207d0bd7d@kernel.org \
--to=dlemoal@kernel.org \
--cc=hanyu001@208suo.com \
--cc=linux-ide@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
all inboxes | Powered by JetHome®