From: kdasaparna@gmail.com
To: gregkh@linuxfoundation.org
Cc: markh@compro.net, lidza.louina@gmail.com,
linux-kernel@vger.kernel.org, devel@driverdev.osuosl.org,
driverdev-devel@linuxdriverproject.org
Subject: [PATCH 3/3] [PATCH] staging: dgnc: Fixed braces {} are not necessary for single statement blocks
Date: Sat, 6 Jun 2015 11:52:54 +0530 [thread overview]
Message-ID: <20150606062254.GC5369@gmail.com> (raw)
Removed the braces of if else statements which contain only one
statement
Signed-off-by: Aparna Karuthodi <kdasaparna@gmail.com>
---
drivers/staging/dgnc/dgnc_tty.c | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/drivers/staging/dgnc/dgnc_tty.c
b/drivers/staging/dgnc/dgnc_tty.c
index f81a375..6cd0b6a 100644
--- a/drivers/staging/dgnc/dgnc_tty.c
+++ b/drivers/staging/dgnc/dgnc_tty.c
@@ -907,7 +907,7 @@ void dgnc_check_queue_flow_control(struct
channel_t *ch)
* 3) NONE - Do nothing. Since we didn't do anything to turn
* off the
* other side, we don't need to do anything now.
*/
- if (qleft > (RQUEUESIZE / 2)) {
+ if (qleft > (RQUEUESIZE / 2))
/* HWFLOW */
if
(ch->ch_digi.digi_flags
& RTSPACE ||
ch->ch_c_cflag
& CRTSCTS) {
if
(ch->ch_flags
&
CH_RECEIVER_OFF)
{
@@
-921,10
+921,10
@@
void
dgnc_check_queue_flow_control(struct
channel_t
*ch)
ch->ch_bd->bd_ops->send_start_character(ch);
}
/* No
* FLOW
* */
- else
{
+
else
/* Nothing
* needed.
* */
- }
- }
+
+
}
--
1.7.9.5
next reply other threads:[~2015-06-06 6:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-06 6:22 kdasaparna [this message]
2015-06-06 8:47 ` [PATCH 3/3] [PATCH] staging: dgnc: Fixed braces {} are not necessary for single statement blocks Dan Carpenter
-- strict thread matches above, loose matches on Subject: below --
2015-07-24 12:46 [PATCH 1/3] [PATCH] staging: lustre: llite: Fix No space after the declaration Aparna Karuthodi
2015-07-24 14:00 ` [PATCH 3/3] [PATCH] staging: dgnc: Fixed braces {} are not necessary for single statement blocks Aparna Karuthodi
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=20150606062254.GC5369@gmail.com \
--to=kdasaparna@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=driverdev-devel@linuxdriverproject.org \
--cc=gregkh@linuxfoundation.org \
--cc=lidza.louina@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=markh@compro.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 an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.