From: Shan Hai <shan.hai@oracle.com>
To: hch@lst.de
Cc: linux-fsdevel@vger.kernel.org
Subject: [PATCH 1/1] iomap: simplify header file include guard macro definition
Date: Mon, 16 Jul 2018 15:07:16 +0800 [thread overview]
Message-ID: <1531724836-7944-1-git-send-email-shan.hai@oracle.com> (raw)
The simple definition of a macro is enough for the include guard, it's not
necessary to assign a value to it, so remove the assignment.
Signed-off-by: Shan Hai <shan.hai@oracle.com>
---
include/linux/iomap.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/include/linux/iomap.h b/include/linux/iomap.h
index a044a82..25aa7d8 100644
--- a/include/linux/iomap.h
+++ b/include/linux/iomap.h
@@ -1,6 +1,6 @@
/* SPDX-License-Identifier: GPL-2.0 */
#ifndef LINUX_IOMAP_H
-#define LINUX_IOMAP_H 1
+#define LINUX_IOMAP_H
#include <linux/types.h>
--
2.7.4
next reply other threads:[~2018-07-16 7:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-16 7:07 Shan Hai [this message]
2018-07-17 13:13 ` [PATCH 1/1] iomap: simplify header file include guard macro definition Christoph Hellwig
2018-07-17 13:47 ` Matthew Wilcox
2018-07-17 13:52 ` Shan Hai
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=1531724836-7944-1-git-send-email-shan.hai@oracle.com \
--to=shan.hai@oracle.com \
--cc=hch@lst.de \
--cc=linux-fsdevel@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.
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 NNTP newsgroup(s).