From: Luis de Bethencourt <luisbg@kernel.org>
To: linux-kernel@vger.kernel.org
Cc: Joe Perches <joe@perches.com>, Vineet Gupta <vgupta@synopsys.com>,
Alexey Brodkin <Alexey.Brodkin@synopsys.com>,
Andrew Morton <akpm@linux-foundation.org>,
Noam Camus <noamca@mellanox.com>,
Vlad Zakharov <Vladislav.Zakharov@synopsys.com>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
Michal Hocko <mhocko@suse.com>,
Stephen Boyd <sboyd@codeaurora.org>,
Masahiro Yamada <yamada.masahiro@socionext.com>,
linux-snps-arc@lists.infradead.org,
Luis de Bethencourt <luisbg@kernel.org>
Subject: [PATCH 1/2] ARC: dw2 unwind: Fix trailing semicolon
Date: Tue, 23 Jan 2018 15:16:08 +0000 [thread overview]
Message-ID: <20180123151609.23555-1-luisbg@kernel.org> (raw)
The trailing semicolon is an empty statement that does no operation.
Removing it since it doesn't do anything.
Signed-off-by: Luis de Bethencourt <luisbg@kernel.org>
---
Hi,
After fixing the same thing in drivers/staging/rtl8723bs/, Joe Perches
suggested I fix it treewide [0].
Best regards
Luis
[0] http://driverdev.linuxdriverproject.org/pipermail/driverdev-devel/2018-January/115410.html
[1] http://driverdev.linuxdriverproject.org/pipermail/driverdev-devel/2018-January/115390.html
arch/arc/kernel/unwind.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arc/kernel/unwind.c b/arch/arc/kernel/unwind.c
index 333daab7def0..183391d4d33a 100644
--- a/arch/arc/kernel/unwind.c
+++ b/arch/arc/kernel/unwind.c
@@ -366,7 +366,7 @@ static void init_unwind_hdr(struct unwind_table *table,
return;
ret_err:
- panic("Attention !!! Dwarf FDE parsing errors\n");;
+ panic("Attention !!! Dwarf FDE parsing errors\n");
}
#ifdef CONFIG_MODULES
--
2.15.1
next reply other threads:[~2018-01-23 15:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-23 15:16 Luis de Bethencourt [this message]
2018-01-23 15:16 ` [PATCH 2/2] ARC: boot log: Fix trailing semicolon Luis de Bethencourt
2018-01-23 19:13 ` Vineet Gupta
2018-01-23 19:13 ` [PATCH 1/2] ARC: dw2 unwind: " Vineet Gupta
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=20180123151609.23555-1-luisbg@kernel.org \
--to=luisbg@kernel.org \
--cc=Alexey.Brodkin@synopsys.com \
--cc=Vladislav.Zakharov@synopsys.com \
--cc=akpm@linux-foundation.org \
--cc=daniel.lezcano@linaro.org \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-snps-arc@lists.infradead.org \
--cc=mhocko@suse.com \
--cc=noamca@mellanox.com \
--cc=sboyd@codeaurora.org \
--cc=vgupta@synopsys.com \
--cc=yamada.masahiro@socionext.com \
/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