All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Biggers <ebiggers@kernel.org>
To: linux-fscrypt@vger.kernel.org
Cc: linux-ext4@vger.kernel.org,
	linux-f2fs-devel@lists.sourceforge.net,
	Jaegeuk Kim <jaegeuk@kernel.org>,
	"Theodore Y . Ts'o" <tytso@mit.edu>,
	Daniel Rosenberg <drosen@google.com>
Subject: [PATCH 1/4] linux/parser.h: add include guards
Date: Tue, 12 May 2020 16:32:48 -0700	[thread overview]
Message-ID: <20200512233251.118314-2-ebiggers@kernel.org> (raw)
In-Reply-To: <20200512233251.118314-1-ebiggers@kernel.org>

From: Eric Biggers <ebiggers@google.com>

<linux/parser.h> is missing include guards.  Add them.

This is needed to allow declaring a function in <linux/fscrypt.h> that
takes a substring_t parameter.

Signed-off-by: Eric Biggers <ebiggers@google.com>
---
 include/linux/parser.h | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/include/linux/parser.h b/include/linux/parser.h
index 12fc3482f5fc7a..89e2b23fb888e8 100644
--- a/include/linux/parser.h
+++ b/include/linux/parser.h
@@ -7,7 +7,8 @@
  * but could potentially be used anywhere else that simple option=arg
  * parsing is required.
  */
-
+#ifndef _LINUX_PARSER_H
+#define _LINUX_PARSER_H
 
 /* associates an integer enumerator with a pattern string. */
 struct match_token {
@@ -34,3 +35,5 @@ int match_hex(substring_t *, int *result);
 bool match_wildcard(const char *pattern, const char *str);
 size_t match_strlcpy(char *, const substring_t *, size_t);
 char *match_strdup(const substring_t *);
+
+#endif /* _LINUX_PARSER_H */
-- 
2.26.2


WARNING: multiple messages have this Message-ID (diff)
From: Eric Biggers <ebiggers@kernel.org>
To: linux-fscrypt@vger.kernel.org
Cc: Jaegeuk Kim <jaegeuk@kernel.org>,
	linux-ext4@vger.kernel.org, "Theodore Y . Ts'o" <tytso@mit.edu>,
	Daniel Rosenberg <drosen@google.com>,
	linux-f2fs-devel@lists.sourceforge.net
Subject: [f2fs-dev] [PATCH 1/4] linux/parser.h: add include guards
Date: Tue, 12 May 2020 16:32:48 -0700	[thread overview]
Message-ID: <20200512233251.118314-2-ebiggers@kernel.org> (raw)
In-Reply-To: <20200512233251.118314-1-ebiggers@kernel.org>

From: Eric Biggers <ebiggers@google.com>

<linux/parser.h> is missing include guards.  Add them.

This is needed to allow declaring a function in <linux/fscrypt.h> that
takes a substring_t parameter.

Signed-off-by: Eric Biggers <ebiggers@google.com>
---
 include/linux/parser.h | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/include/linux/parser.h b/include/linux/parser.h
index 12fc3482f5fc7a..89e2b23fb888e8 100644
--- a/include/linux/parser.h
+++ b/include/linux/parser.h
@@ -7,7 +7,8 @@
  * but could potentially be used anywhere else that simple option=arg
  * parsing is required.
  */
-
+#ifndef _LINUX_PARSER_H
+#define _LINUX_PARSER_H
 
 /* associates an integer enumerator with a pattern string. */
 struct match_token {
@@ -34,3 +35,5 @@ int match_hex(substring_t *, int *result);
 bool match_wildcard(const char *pattern, const char *str);
 size_t match_strlcpy(char *, const substring_t *, size_t);
 char *match_strdup(const substring_t *);
+
+#endif /* _LINUX_PARSER_H */
-- 
2.26.2



_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel

  reply	other threads:[~2020-05-12 23:36 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-12 23:32 [PATCH 0/4] fscrypt: make '-o test_dummy_encryption' support v2 policies Eric Biggers
2020-05-12 23:32 ` [f2fs-dev] " Eric Biggers
2020-05-12 23:32 ` Eric Biggers [this message]
2020-05-12 23:32   ` [f2fs-dev] [PATCH 1/4] linux/parser.h: add include guards Eric Biggers
2020-05-13  0:53   ` Theodore Y. Ts'o
2020-05-13  0:53     ` [f2fs-dev] " Theodore Y. Ts'o
2020-05-13  3:06     ` Jaegeuk Kim
2020-05-13  3:06       ` [f2fs-dev] " Jaegeuk Kim
2020-05-12 23:32 ` [PATCH 2/4] fscrypt: add fscrypt_add_test_dummy_key() Eric Biggers
2020-05-12 23:32   ` [f2fs-dev] " Eric Biggers
2020-05-13  0:55   ` Theodore Y. Ts'o
2020-05-13  0:55     ` [f2fs-dev] " Theodore Y. Ts'o
2020-05-13  3:07     ` Jaegeuk Kim
2020-05-13  3:07       ` [f2fs-dev] " Jaegeuk Kim
2020-05-12 23:32 ` [PATCH 3/4] fscrypt: support test_dummy_encryption=v2 Eric Biggers
2020-05-12 23:32   ` [f2fs-dev] " Eric Biggers
2020-05-13  3:11   ` Jaegeuk Kim
2020-05-13  3:11     ` [f2fs-dev] " Jaegeuk Kim
2020-05-19  2:53   ` Theodore Y. Ts'o
2020-05-19  2:53     ` [f2fs-dev] " Theodore Y. Ts'o
2020-05-19  3:02     ` Eric Biggers
2020-05-19  3:02       ` [f2fs-dev] " Eric Biggers
2020-05-19  3:11       ` Eric Biggers
2020-05-19  3:11         ` [f2fs-dev] " Eric Biggers
2020-05-19  3:19         ` Jaegeuk Kim
2020-05-19  3:19           ` [f2fs-dev] " Jaegeuk Kim
2020-05-19 14:02       ` Theodore Y. Ts'o
2020-05-19 14:02         ` [f2fs-dev] " Theodore Y. Ts'o
2020-05-12 23:32 ` [PATCH 4/4] fscrypt: make test_dummy_encryption use v2 by default Eric Biggers
2020-05-12 23:32   ` [f2fs-dev] " Eric Biggers
2020-05-13  3:12   ` Jaegeuk Kim
2020-05-13  3:12     ` [f2fs-dev] " Jaegeuk Kim
2020-05-19  2:55   ` Theodore Y. Ts'o
2020-05-19  2:55     ` [f2fs-dev] " Theodore Y. Ts'o
2020-05-20 22:55 ` [PATCH 0/4] fscrypt: make '-o test_dummy_encryption' support v2 policies Eric Biggers
2020-05-20 22:55   ` [f2fs-dev] " Eric Biggers

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=20200512233251.118314-2-ebiggers@kernel.org \
    --to=ebiggers@kernel.org \
    --cc=drosen@google.com \
    --cc=jaegeuk@kernel.org \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    --cc=linux-fscrypt@vger.kernel.org \
    --cc=tytso@mit.edu \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.