From: Geert Uytterhoeven <geert@linux-m68k.org>
To: linux-m68k@lists.linux-m68k.org
Cc: Arnd Bergmann <arnd@arndb.de>,
linux-kernel@vger.kernel.org,
Geert Uytterhoeven <geert@linux-m68k.org>
Subject: [PATCH 2/6] m68k: math-emu: Sanitize include guards
Date: Thu, 17 Aug 2023 16:44:49 +0200 [thread overview]
Message-ID: <8c84c8bf06c0c1e463c47f071891e2e83d5abdd2.1692283195.git.geert@linux-m68k.org> (raw)
In-Reply-To: <cover.1692283195.git.geert@linux-m68k.org>
Some include guards start with an underscore, others don't.
Some comments do not match the actual include guard.
Make them uniform, adhering to the "FP_<FOO>_H" format.
Signed-off-by: Geert Uytterhoeven <geert@linux-m68k.org>
---
arch/m68k/math-emu/fp_arith.h | 6 +++---
arch/m68k/math-emu/fp_trig.h | 6 +++---
arch/m68k/math-emu/multi_arith.h | 6 +++---
3 files changed, 9 insertions(+), 9 deletions(-)
diff --git a/arch/m68k/math-emu/fp_arith.h b/arch/m68k/math-emu/fp_arith.h
index 0fd3ed217f668652..85bdd83b9dd667a8 100644
--- a/arch/m68k/math-emu/fp_arith.h
+++ b/arch/m68k/math-emu/fp_arith.h
@@ -12,8 +12,8 @@
*/
-#ifndef FP_ARITH_H
-#define FP_ARITH_H
+#ifndef _FP_ARITH_H
+#define _FP_ARITH_H
/* easy ones */
struct fp_ext *
@@ -47,4 +47,4 @@ fp_fintrz(struct fp_ext *dest, struct fp_ext *src);
struct fp_ext *
fp_fscale(struct fp_ext *dest, struct fp_ext *src);
-#endif /* FP_ARITH__H */
+#endif /* _FP_ARITH_H */
diff --git a/arch/m68k/math-emu/fp_trig.h b/arch/m68k/math-emu/fp_trig.h
index af8b247e9c982874..52f0cc31cfe49cb7 100644
--- a/arch/m68k/math-emu/fp_trig.h
+++ b/arch/m68k/math-emu/fp_trig.h
@@ -15,8 +15,8 @@
*/
-#ifndef FP_TRIG_H
-#define FP_TRIG_H
+#ifndef _FP_TRIG_H
+#define _FP_TRIG_H
#include "fp_emu.h"
@@ -29,4 +29,4 @@
they return a status code, which should end up in %d0, if all goes
well. */
-#endif /* FP_TRIG__H */
+#endif /* _FP_TRIG_H */
diff --git a/arch/m68k/math-emu/multi_arith.h b/arch/m68k/math-emu/multi_arith.h
index 232f58fe3483d2be..ed2434fcfb1ef46e 100644
--- a/arch/m68k/math-emu/multi_arith.h
+++ b/arch/m68k/math-emu/multi_arith.h
@@ -15,8 +15,8 @@
implement the subset of integer arithmetic that we need in order to
multiply, divide, and normalize 128-bit unsigned mantissae. */
-#ifndef MULTI_ARITH_H
-#define MULTI_ARITH_H
+#ifndef _MULTI_ARITH_H
+#define _MULTI_ARITH_H
static inline void fp_denormalize(struct fp_ext *reg, unsigned int cnt)
{
@@ -285,4 +285,4 @@ static inline void fp_putmant128(struct fp_ext *dest, union fp_mant128 *src,
}
}
-#endif /* MULTI_ARITH_H */
+#endif /* _MULTI_ARITH_H */
--
2.34.1
next prev parent reply other threads:[~2023-08-17 14:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-17 14:44 [PATCH 0/6] m68k: math-emu: Miscellaneous esthetical improvements Geert Uytterhoeven
2023-08-17 14:44 ` [PATCH 1/6] m68k: math-emu: Fix incorrect file reference in fp_log.c Geert Uytterhoeven
2023-08-17 14:44 ` Geert Uytterhoeven [this message]
2023-08-17 14:44 ` [PATCH 3/6] m68k: math-emu: Make multi_arith.h self-contained Geert Uytterhoeven
2023-08-17 14:44 ` [PATCH 4/6] m68k: math-emu: Replace external declarations by header inclusion Geert Uytterhoeven
2023-08-17 14:44 ` [PATCH 5/6] m68k: math-emu: Reformat function and variable headers Geert Uytterhoeven
2023-08-17 14:44 ` [PATCH 6/6] m68k: math-emu: Add missing prototypes Geert Uytterhoeven
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=8c84c8bf06c0c1e463c47f071891e2e83d5abdd2.1692283195.git.geert@linux-m68k.org \
--to=geert@linux-m68k.org \
--cc=arnd@arndb.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.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
all inboxes | Powered by JetHome®