From: Jiapeng Chong <jiapeng.chong@linux.alibaba.com>
To: tim@cyberelk.net
Cc: axboe@kernel.dk, linux-block@vger.kernel.org,
linux-kernel@vger.kernel.org,
Jiapeng Chong <jiapeng.chong@linux.alibaba.com>,
Abaci Robot <abaci@linux.alibaba.com>
Subject: [PATCH] paride: clean up some inconsistent indenting
Date: Sun, 26 Dec 2021 01:07:04 +0800 [thread overview]
Message-ID: <20211225170704.113893-1-jiapeng.chong@linux.alibaba.com> (raw)
Eliminate the follow smatch warning:
drivers/block/paride/bpck.c:66 bpck_read_regr() warn: inconsistent
indenting.
drivers/block/paride/bpck.c:294 bpck_test_proto() warn: inconsistent
indenting.
Reported-by: Abaci Robot <abaci@linux.alibaba.com>
Signed-off-by: Jiapeng Chong <jiapeng.chong@linux.alibaba.com>
---
drivers/block/paride/bpck.c | 20 ++++++++++----------
1 file changed, 10 insertions(+), 10 deletions(-)
diff --git a/drivers/block/paride/bpck.c b/drivers/block/paride/bpck.c
index d880a9465e9b..e7f97620fb63 100644
--- a/drivers/block/paride/bpck.c
+++ b/drivers/block/paride/bpck.c
@@ -55,16 +55,16 @@ static int bpck_read_regr( PIA *pi, int cont, int regr )
switch (pi->mode) {
case 0: w0(r & 0xf); w0(r); t2(2); t2(4);
- l = r1();
- t2(4);
- h = r1();
- return j44(l,h);
+ l = r1();
+ t2(4);
+ h = r1();
+ return j44(l, h);
case 1: w0(r & 0xf); w0(r); t2(2);
- e2(); t2(0x20);
+ e2(); t2(0x20);
t2(4); h = r0();
- t2(1); t2(0x20);
- return h;
+ t2(1); t2(0x20);
+ return h;
case 2:
case 3:
@@ -289,9 +289,9 @@ static int bpck_test_proto( PIA *pi, char * scratch, int verbose )
WR(0x13,0x7f);
w0(0x13); t2(2);
for(i=0;i<TEST_LEN;i++) {
- t2(4); l = r1();
- t2(4); h = r1();
- buf[i] = j44(l,h);
+ t2(4); l = r1();
+ t2(4); h = r1();
+ buf[i] = j44(l, h);
}
bpck_disconnect(pi);
break;
--
2.20.1.7.g153144c
next reply other threads:[~2021-12-25 17:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-25 17:07 Jiapeng Chong [this message]
2022-08-04 8:13 [PATCH] paride: Clean " Jiapeng Chong
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=20211225170704.113893-1-jiapeng.chong@linux.alibaba.com \
--to=jiapeng.chong@linux.alibaba.com \
--cc=abaci@linux.alibaba.com \
--cc=axboe@kernel.dk \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tim@cyberelk.net \
/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®