From: hanyu001@208suo.com
To: dlemoal@kernel.org
Cc: linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH] drivers: ata: Added missing spaces
Date: Tue, 18 Jul 2023 17:12:49 +0800 [thread overview]
Message-ID: <c34db7fdcd7ac86046fe481cb91a9a48@208suo.com> (raw)
In-Reply-To: <tencent_BF5CCE8322052C3E2AE2861606F1D8AE740A@qq.com>
Added spaces needed in the proper places to address:
./drivers/ata/pata_triflex.c:88: ERROR: space required after that ';'
(ctx:VxV)
./drivers/ata/pata_triflex.c:90: ERROR: space required after that ';'
(ctx:VxV)
./drivers/ata/pata_triflex.c:92: ERROR: space required after that ';'
(ctx:VxV)
./drivers/ata/pata_triflex.c:96: ERROR: space required after that ';'
(ctx:VxV)
./drivers/ata/pata_triflex.c:98: ERROR: space required after that ';'
(ctx:VxV)
./drivers/ata/pata_triflex.c:100: ERROR: space required after that ';'
(ctx:VxV)
./drivers/ata/pata_triflex.c:102: ERROR: space required after that ';'
(ctx:VxV)
./drivers/ata/pata_triflex.c:104: ERROR: space required after that ';'
(ctx:VxV)
./drivers/ata/pata_triflex.c:106: ERROR: space required after that ';'
(ctx:VxV)
Signed-off-by: Yu Han <hanyu001@208suo.com>
---
drivers/ata/pata_triflex.c | 18 +++++++++---------
1 file changed, 9 insertions(+), 9 deletions(-)
diff --git a/drivers/ata/pata_triflex.c b/drivers/ata/pata_triflex.c
index 26d448a..e75bf93 100644
--- a/drivers/ata/pata_triflex.c
+++ b/drivers/ata/pata_triflex.c
@@ -85,25 +85,25 @@ static void triflex_load_timing(struct ata_port *ap,
struct ata_device *adev, in
switch(speed)
{
case XFER_MW_DMA_2:
- timing = 0x0103;break;
+ timing = 0x0103; break;
case XFER_MW_DMA_1:
- timing = 0x0203;break;
+ timing = 0x0203; break;
case XFER_MW_DMA_0:
- timing = 0x0808;break;
+ timing = 0x0808; break;
case XFER_SW_DMA_2:
case XFER_SW_DMA_1:
case XFER_SW_DMA_0:
- timing = 0x0F0F;break;
+ timing = 0x0F0F; break;
case XFER_PIO_4:
- timing = 0x0202;break;
+ timing = 0x0202; break;
case XFER_PIO_3:
- timing = 0x0204;break;
+ timing = 0x0204; break;
case XFER_PIO_2:
- timing = 0x0404;break;
+ timing = 0x0404; break;
case XFER_PIO_1:
- timing = 0x0508;break;
+ timing = 0x0508; break;
case XFER_PIO_0:
- timing = 0x0808;break;
+ timing = 0x0808; break;
default:
BUG();
}
next parent reply other threads:[~2023-07-18 9:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <tencent_BF5CCE8322052C3E2AE2861606F1D8AE740A@qq.com>
2023-07-18 9:12 ` hanyu001 [this message]
2023-07-18 9:46 ` Sergey Shtylyov
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=c34db7fdcd7ac86046fe481cb91a9a48@208suo.com \
--to=hanyu001@208suo.com \
--cc=dlemoal@kernel.org \
--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®