From: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
To: smatch@vger.kernel.org
Cc: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Subject: [PATCH] continue_vs_break: Fix some style issue
Date: Thu, 25 Aug 2022 19:38:36 +0200 [thread overview]
Message-ID: <e32eb5c3455857d64fc6f051d2a2174bdf1d840f.1661449100.git.christophe.jaillet@wanadoo.fr> (raw)
Add a missing } in a comment.
Remove some unneeded {} in code, to be consistent.
Signed-off-by: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
---
check_continue_vs_break.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/check_continue_vs_break.c b/check_continue_vs_break.c
index d12577e0e6d2..6c991630d3d9 100644
--- a/check_continue_vs_break.c
+++ b/check_continue_vs_break.c
@@ -20,6 +20,7 @@
* do {
* if (xxx)
* continue;
+ * }
* while (0);
*
* Then the continue is equivalent of a break. So what was really intended?
@@ -76,9 +77,9 @@ static void match_stmt(struct statement *stmt)
if (stmt->type != STMT_ITERATOR)
return;
- if (is_do_while_zero(stmt)) {
+ if (is_do_while_zero(stmt))
push_statement(&iterator_stack, stmt);
- } else
+ else
push_statement(&iterator_stack, NULL);
}
--
2.34.1
reply other threads:[~2022-08-25 17:38 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=e32eb5c3455857d64fc6f051d2a2174bdf1d840f.1661449100.git.christophe.jaillet@wanadoo.fr \
--to=christophe.jaillet@wanadoo.fr \
--cc=smatch@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 read-only IMAP folder(s) and NNTP newsgroup(s).