linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: trix@redhat.com
To: peterz@infradead.org, mingo@redhat.com, will@kernel.org
Cc: linux-kernel@vger.kernel.org, Tom Rix <trix@redhat.com>
Subject: [PATCH] locking/selftest: remove trailing semicolon in macro definition
Date: Fri, 27 Nov 2020 11:36:04 -0800	[thread overview]
Message-ID: <20201127193604.2873370-1-trix@redhat.com> (raw)

From: Tom Rix <trix@redhat.com>

The macro use will already have a semicolon.

Signed-off-by: Tom Rix <trix@redhat.com>
---
 lib/locking-selftest.c | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/lib/locking-selftest.c b/lib/locking-selftest.c
index a899b3f0e2e5..69b4a1160094 100644
--- a/lib/locking-selftest.c
+++ b/lib/locking-selftest.c
@@ -935,7 +935,7 @@ GENERATE_PERMUTATIONS_3_EVENTS(irqsafe3_soft_wlock)
 	LOCK(B);			\
 	UNLOCK(B);			\
 	UNLOCK(A);			\
-	IRQ_ENABLE();
+	IRQ_ENABLE()
 
 #define E2()				\
 	LOCK(B);			\
@@ -995,7 +995,7 @@ GENERATE_PERMUTATIONS_3_EVENTS(irqsafe4_soft_wlock)
 	LOCK(B);			\
 	UNLOCK(B);			\
 	WU(A);				\
-	IRQ_ENABLE();
+	IRQ_ENABLE()
 
 #define E2()				\
 					\
@@ -1170,7 +1170,7 @@ GENERATE_PERMUTATIONS_3_EVENTS(W1W2_R2R3_R3W1)
 	IRQ_DISABLE();			\
 	WL(A);				\
 	WU(A);				\
-	IRQ_ENABLE();
+	IRQ_ENABLE()
 
 #define E2()				\
 					\
@@ -1218,7 +1218,7 @@ GENERATE_PERMUTATIONS_3_EVENTS(irq_read_recursion_soft_wlock)
 	LOCK(A);			\
 	UNLOCK(A);			\
 	U(B);				\
-	IRQ_ENABLE();
+	IRQ_ENABLE()
 
 #define E2()				\
 					\
@@ -1272,7 +1272,7 @@ GENERATE_PERMUTATIONS_3_EVENTS(irq_read_recursion2_soft_wlock)
 	LOCK(A);			\
 	UNLOCK(A);			\
 	WU(B);				\
-	IRQ_ENABLE();
+	IRQ_ENABLE()
 
 #define E2()				\
 					\
-- 
2.18.4


                 reply	other threads:[~2020-11-27 19:59 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=20201127193604.2873370-1-trix@redhat.com \
    --to=trix@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=will@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).