From: Nikolay Kyx <knv418@gmail.com>
To: gregkh@linuxfoundation.org, adawesomeguy222@gmail.com,
dinghao.liu@zju.edu.cn
Cc: Nikolay Kyx <knv418@gmail.com>,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: [PATCH v3] staging: fwserial: match alignment with open parenthesis
Date: Fri, 19 Feb 2021 18:49:17 +0300 [thread overview]
Message-ID: <20210219154917.23388-1-knv418@gmail.com> (raw)
In-Reply-To: <20210219092918.GV2087@kadam>
This patch fixes the following checkpatch.pl check:
CHECK: Alignment should match open parenthesis
in file fwserial.c
Signed-off-by: Nikolay Kyx <knv418@gmail.com>
---
Additionally some style warnings remain valid here and could be fixed by
another patch.
v2: Edited changelog, as suggested by Greg KH <gregkh@linuxfoundation.org>
v3: Moved comment about remaining warnings under the cut-off line,
as suggested by Dan Carpenter <dan.carpenter@oracle.com>
drivers/staging/fwserial/fwserial.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/staging/fwserial/fwserial.c b/drivers/staging/fwserial/fwserial.c
index c368082aae1a..137e97c9406c 100644
--- a/drivers/staging/fwserial/fwserial.c
+++ b/drivers/staging/fwserial/fwserial.c
@@ -1318,8 +1318,8 @@ static int fwtty_break_ctl(struct tty_struct *tty, int state)
if (state == -1) {
set_bit(STOP_TX, &port->flags);
ret = wait_event_interruptible_timeout(port->wait_tx,
- !test_bit(IN_TX, &port->flags),
- 10);
+ !test_bit(IN_TX, &port->flags),
+ 10);
if (ret == 0 || ret == -ERESTARTSYS) {
clear_bit(STOP_TX, &port->flags);
fwtty_restart_tx(port);
--
2.30.1
prev parent reply other threads:[~2021-02-19 15:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-18 19:43 [PATCH] staging: fwserial: match alignment with open parenthesis Nikolay Kyx
2021-02-19 8:14 ` Greg KH
2021-02-19 9:03 ` [PATCH v2] " Nikolay Kyx
2021-02-19 9:29 ` Dan Carpenter
2021-02-19 15:49 ` Nikolay Kyx [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=20210219154917.23388-1-knv418@gmail.com \
--to=knv418@gmail.com \
--cc=adawesomeguy222@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=dinghao.liu@zju.edu.cn \
--cc=gregkh@linuxfoundation.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).