From: Abhishek Kumar <abhishekkumar8222@gmail.com>
To: git@vger.kernel.org
Subject: [PATCH v2] commit-slab-decl.h: fix define guards
Date: Mon, 18 May 2020 20:00:23 +0530 [thread overview]
Message-ID: <20200518143023.14217-1-abhishekkumar8222@gmail.com> (raw)
In-Reply-To: <20200516172837.2872-1-abhishekkumar8222@gmail.com>
a9f1f1f9f8 ("commit-slab.h: code split", 2018-05-19) split commit-slab
into commit-slab-decl and commit-slab-impl header files. The define
guards for commit-slab-decl still use "COMMIT_SLAB_HDR_H". Fortunately,
commit-slab-impl introduced its own macro, "COMMIT_SLAB_IMPL_H".
Otherwise, the code would have been broken by not including
commit-slab-impl.
Let's correct the define guards for commit-slab-decl to match file name.
Signed-off-by: Abhishek Kumar <abhishekkumar8222@gmail.com>
---
commit-slab-decl.h | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/commit-slab-decl.h b/commit-slab-decl.h
index adc7b46c83..bfbed1516a 100644
--- a/commit-slab-decl.h
+++ b/commit-slab-decl.h
@@ -1,5 +1,5 @@
-#ifndef COMMIT_SLAB_HDR_H
-#define COMMIT_SLAB_HDR_H
+#ifndef COMMIT_SLAB_DECL_H
+#define COMMIT_SLAB_DECL_H
/* allocate ~512kB at once, allowing for malloc overhead */
#ifndef COMMIT_SLAB_SIZE
@@ -40,4 +40,4 @@ elemtype *slabname## _peek(struct slabname *s, const struct commit *c)
declare_commit_slab(slabname, elemtype); \
declare_commit_slab_prototypes(slabname, elemtype)
-#endif /* COMMIT_SLAB_HDR_H */
+#endif /* COMMIT_SLAB_DECL_H */
--
2.26.0
next prev parent reply other threads:[~2020-05-18 14:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-16 17:28 [PATCH] commit-slab-decl.h: fix define gaurds Abhishek Kumar
2020-05-17 15:44 ` Junio C Hamano
2020-05-18 14:30 ` Abhishek Kumar [this message]
2020-05-18 17:12 ` [PATCH v2] commit-slab-decl.h: fix define guards Junio C Hamano
2020-05-18 17:29 ` Eric Sunshine
2020-05-18 17:32 ` Junio C Hamano
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200518143023.14217-1-abhishekkumar8222@gmail.com \
--to=abhishekkumar8222@gmail.com \
--cc=git@vger.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).