From: Vishal Verma <vishal.l.verma@intel.com>
To: nvdimm@lists.linux.dev
Cc: Dan Williams <dan.j.williams@intel.com>,
Alison Schofield <alison.schofield@intel.com>,
Vishal Verma <vishal.l.verma@intel.com>,
linux-cxl@vger.kernel.org
Subject: [PATCH ndctl 1/2] clang-format: Align consecutive macros and #defines
Date: Tue, 06 Dec 2022 15:46:23 -0700 [thread overview]
Message-ID: <20221206-vv-misc-v1-1-4c5bd58c90ca@intel.com> (raw)
In-Reply-To: <20221206-vv-misc-v1-0-4c5bd58c90ca@intel.com>
Add AlignConsecutiveMacros: true so that blocks of consecutive #defines
can be neatly aligned.
Cc: Dan Williams <dan.j.williams@intel.com>
Reported-by: Alison Schofield <alison.schofield@intel.com>
Signed-off-by: Vishal Verma <vishal.l.verma@intel.com>
---
.clang-format | 1 +
1 file changed, 1 insertion(+)
diff --git a/.clang-format b/.clang-format
index b6169e1..9ea49bf 100644
--- a/.clang-format
+++ b/.clang-format
@@ -13,6 +13,7 @@ AccessModifierOffset: -4
AlignAfterOpenBracket: Align
AlignConsecutiveAssignments: false
AlignConsecutiveDeclarations: false
+AlignConsecutiveMacros: true
#AlignEscapedNewlines: Left # Unknown to clang-format-4.0
AlignOperands: true
AlignTrailingComments: false
--
2.38.1
next prev parent reply other threads:[~2022-12-06 22:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-06 22:46 [PATCH ndctl 0/2] misc meson.build and clang-format updates Vishal Verma
2022-12-06 22:46 ` Vishal Verma [this message]
2022-12-07 1:12 ` [PATCH ndctl 1/2] clang-format: Align consecutive macros and #defines Alison Schofield
2022-12-06 22:46 ` [PATCH ndctl 2/2] meson.build: add a check argument to run_command Vishal Verma
2022-12-07 21:48 ` Dan Williams
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=20221206-vv-misc-v1-1-4c5bd58c90ca@intel.com \
--to=vishal.l.verma@intel.com \
--cc=alison.schofield@intel.com \
--cc=dan.j.williams@intel.com \
--cc=linux-cxl@vger.kernel.org \
--cc=nvdimm@lists.linux.dev \
/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