From: Ammar Faizi <[email protected]>
To: Jens Axboe <[email protected]>
Cc: Ammar Faizi <[email protected]>,
Alviro Iskandar Setiawan <[email protected]>,
Fernanda Ma'rouf <[email protected]>,
Hao Xu <[email protected]>,
Pavel Begunkov <[email protected]>,
io-uring Mailing List <[email protected]>,
GNU/Weeb Mailing List <[email protected]>
Subject: [PATCH liburing v3 06/10] lib: Style fixup for #if / #elif / #else / #endif
Date: Tue, 5 Jul 2022 00:54:32 +0700 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
From: Ammar Faizi <[email protected]>
Don't indent the block inside #if / #elif / #else / #endif.
Signed-off-by: Ammar Faizi <[email protected]>
---
src/lib.h | 28 ++++++++++++++--------------
1 file changed, 14 insertions(+), 14 deletions(-)
diff --git a/src/lib.h b/src/lib.h
index 7bbacb9..a966c77 100644
--- a/src/lib.h
+++ b/src/lib.h
@@ -7,28 +7,28 @@
#include <unistd.h>
#if defined(__x86_64__) || defined(__i386__)
- #include "arch/x86/lib.h"
+#include "arch/x86/lib.h"
#else
- /*
- * We don't have nolibc support for this arch. Must use libc!
- */
- #ifdef CONFIG_NOLIBC
- #error "This arch doesn't support building liburing without libc"
- #endif
- /* libc wrappers. */
- #include "arch/generic/lib.h"
+/*
+ * We don't have nolibc support for this arch. Must use libc!
+ */
+#ifdef CONFIG_NOLIBC
+#error "This arch doesn't support building liburing without libc"
+#endif
+/* libc wrappers. */
+#include "arch/generic/lib.h"
#endif
#ifndef offsetof
- #define offsetof(TYPE, FIELD) ((size_t) &((TYPE *)0)->FIELD)
+#define offsetof(TYPE, FIELD) ((size_t) &((TYPE *)0)->FIELD)
#endif
#ifndef container_of
- #define container_of(PTR, TYPE, FIELD) ({ \
- __typeof__(((TYPE *)0)->FIELD) *__FIELD_PTR = (PTR); \
- (TYPE *)((char *) __FIELD_PTR - offsetof(TYPE, FIELD)); \
- })
+#define container_of(PTR, TYPE, FIELD) ({ \
+ __typeof__(((TYPE *)0)->FIELD) *__FIELD_PTR = (PTR); \
+ (TYPE *)((char *) __FIELD_PTR - offsetof(TYPE, FIELD)); \
+})
#endif
#define __maybe_unused __attribute__((__unused__))
--
Ammar Faizi
next prev parent reply other threads:[~2022-07-04 17:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-04 17:54 [PATCH liburing v3 00/10] aarch64 support Ammar Faizi
2022-07-04 17:54 ` [PATCH liburing v3 01/10] CHANGELOG: Fixup missing space Ammar Faizi
2022-07-04 17:54 ` [PATCH liburing v3 02/10] arch: syscall: Add `__sys_open()` syscall Ammar Faizi
2022-07-04 18:07 ` Alviro Iskandar Setiawan
2022-07-04 17:54 ` [PATCH liburing v3 03/10] arch: syscall: Add `__sys_read()` syscall Ammar Faizi
2022-07-04 18:12 ` Alviro Iskandar Setiawan
2022-07-04 18:16 ` Ammar Faizi
2022-07-04 17:54 ` [PATCH liburing v3 04/10] arch: Remove `__INTERNAL__LIBURING_LIB_H` checks Ammar Faizi
2022-07-04 17:54 ` [PATCH liburing v3 05/10] arch/aarch64: lib: Add `get_page_size()` function Ammar Faizi
2022-07-04 18:18 ` Alviro Iskandar Setiawan
2022-07-04 18:23 ` Ammar Faizi
2022-07-04 17:54 ` Ammar Faizi [this message]
2022-07-04 17:54 ` [PATCH liburing v3 07/10] lib: Enable nolibc support for aarch64 Ammar Faizi
2022-07-04 17:54 ` [PATCH liburing v3 08/10] test: Add nolibc test Ammar Faizi
2022-07-04 17:54 ` [PATCH liburing v3 09/10] .github: Enable aarch64 nolibc build for GitHub bot Ammar Faizi
2022-07-04 17:54 ` [PATCH liburing v3 10/10] CHANGELOG: Note about aarch64 support Ammar Faizi
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 \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/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