mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dishank Jogi <jogidishank503@gmail.com>
To: elver@google.com
Cc: dvyukov@google.com, kasan-dev@googlegroups.com,
	linux-kernel@vger.kernel.org, rathod.darshan.0896@gmail.com,
	Dishank Jogi <jogidishank503@gmail.com>
Subject: [PATCH] kcsan: clean up redundant empty macro arguments in atomic ops.
Date: Mon, 28 Jul 2025 10:43:27 +0000	[thread overview]
Message-ID: <20250728104327.48469-1-jogidishank503@gmail.com> (raw)

---------------------------------------------------------

- Removed unnecessary trailing commas from DEFINE_TSAN_ATOMIC_RMW() macro
  calls within DEFINE_TSAN_ATOMIC_OPS() in kernel/kcsan/core.c

- It passes checkpatch.pl with no errors or warnings and
  introduces no functional changes.

---------------------------------------------------------

Signed-off-by: Dishank Jogi <jogidishank503@gmail.com>
---
 kernel/kcsan/core.c | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/kernel/kcsan/core.c b/kernel/kcsan/core.c
index 8a7baf4e332e..f2ec7fa4a44d 100644
--- a/kernel/kcsan/core.c
+++ b/kernel/kcsan/core.c
@@ -1257,12 +1257,12 @@ static __always_inline void kcsan_atomic_builtin_memorder(int memorder)
 #define DEFINE_TSAN_ATOMIC_OPS(bits)                                                               \
 	DEFINE_TSAN_ATOMIC_LOAD_STORE(bits);                                                       \
 	DEFINE_TSAN_ATOMIC_RMW(exchange, bits, _n);                                                \
-	DEFINE_TSAN_ATOMIC_RMW(fetch_add, bits, );                                                 \
-	DEFINE_TSAN_ATOMIC_RMW(fetch_sub, bits, );                                                 \
-	DEFINE_TSAN_ATOMIC_RMW(fetch_and, bits, );                                                 \
-	DEFINE_TSAN_ATOMIC_RMW(fetch_or, bits, );                                                  \
-	DEFINE_TSAN_ATOMIC_RMW(fetch_xor, bits, );                                                 \
-	DEFINE_TSAN_ATOMIC_RMW(fetch_nand, bits, );                                                \
+	DEFINE_TSAN_ATOMIC_RMW(fetch_add, bits);                                                 \
+	DEFINE_TSAN_ATOMIC_RMW(fetch_sub, bits);                                                 \
+	DEFINE_TSAN_ATOMIC_RMW(fetch_and, bits);                                                 \
+	DEFINE_TSAN_ATOMIC_RMW(fetch_or, bits);                                                  \
+	DEFINE_TSAN_ATOMIC_RMW(fetch_xor, bits);                                                 \
+	DEFINE_TSAN_ATOMIC_RMW(fetch_nand, bits);                                                \
 	DEFINE_TSAN_ATOMIC_CMPXCHG(bits, strong, 0);                                               \
 	DEFINE_TSAN_ATOMIC_CMPXCHG(bits, weak, 1);                                                 \
 	DEFINE_TSAN_ATOMIC_CMPXCHG_VAL(bits)
-- 
2.43.0


             reply	other threads:[~2025-07-28 10:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-28 10:43 Dishank Jogi [this message]
2025-07-28 10:55 ` Marco Elver
     [not found]   ` <CADorM--0n1zeT8jxT3LtjmqrP5Cp1g-hFS=oz_12SptjZwRWtw@mail.gmail.com>
2025-07-28 11:51     ` Marco Elver
2025-07-28 20:31 ` kernel test robot
2025-07-28 21:44 ` kernel test robot
2025-07-29  5:17   ` Jogi Dishank

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=20250728104327.48469-1-jogidishank503@gmail.com \
    --to=jogidishank503@gmail.com \
    --cc=dvyukov@google.com \
    --cc=elver@google.com \
    --cc=kasan-dev@googlegroups.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rathod.darshan.0896@gmail.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

all inboxes | Powered by JetHome®