From: Christoph Hellwig <hch@lst.de>
To: Alexander Viro <viro@zeniv.linux.org.uk>,
Christian Brauner <brauner@kernel.org>
Cc: Jan Kara <jack@suse.cz>, linux-fsdevel@vger.kernel.org
Subject: [PATCH 1/4] fs: mark bool_names static
Date: Thu, 19 Feb 2026 07:50:01 +0100 [thread overview]
Message-ID: <20260219065014.3550402-2-hch@lst.de> (raw)
In-Reply-To: <20260219065014.3550402-1-hch@lst.de>
The bool_names array is only used in fs_parser.c so mark it static.
Signed-off-by: Christoph Hellwig <hch@lst.de>
---
fs/fs_parser.c | 3 +--
include/linux/fs_parser.h | 2 --
2 files changed, 1 insertion(+), 4 deletions(-)
diff --git a/fs/fs_parser.c b/fs/fs_parser.c
index c092a9f79e32..46993e31137d 100644
--- a/fs/fs_parser.c
+++ b/fs/fs_parser.c
@@ -13,7 +13,7 @@
#include <linux/namei.h>
#include "internal.h"
-const struct constant_table bool_names[] = {
+static const struct constant_table bool_names[] = {
{ "0", false },
{ "1", true },
{ "false", false },
@@ -22,7 +22,6 @@ const struct constant_table bool_names[] = {
{ "yes", true },
{ },
};
-EXPORT_SYMBOL(bool_names);
static const struct constant_table *
__lookup_constant(const struct constant_table *tbl, const char *name)
diff --git a/include/linux/fs_parser.h b/include/linux/fs_parser.h
index 5e8a3b546033..ac8253cca2bc 100644
--- a/include/linux/fs_parser.h
+++ b/include/linux/fs_parser.h
@@ -84,8 +84,6 @@ extern int fs_lookup_param(struct fs_context *fc,
extern int lookup_constant(const struct constant_table tbl[], const char *name, int not_found);
-extern const struct constant_table bool_names[];
-
#ifdef CONFIG_VALIDATE_FS_PARSER
extern bool fs_validate_description(const char *name,
const struct fs_parameter_spec *desc);
--
2.47.3
next prev parent reply other threads:[~2026-02-19 6:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-19 6:50 remove or unexport unused fs_conext infrastructure Christoph Hellwig
2026-02-19 6:50 ` Christoph Hellwig [this message]
2026-02-19 6:50 ` [PATCH 2/4] fs: remove fsparam_blob / fs_param_is_blob Christoph Hellwig
2026-02-19 6:50 ` [PATCH 3/4] fs: remove fsparam_path / fs_param_is_path Christoph Hellwig
2026-02-19 16:04 ` Darrick J. Wong
2026-02-20 15:24 ` Christoph Hellwig
2026-02-20 18:21 ` Darrick J. Wong
2026-02-19 6:50 ` [PATCH 4/4] fs: unexport fs_context_for_reconfigure Christoph Hellwig
2026-02-19 11:45 ` remove or unexport unused fs_conext infrastructure Jan Kara
2026-02-19 13:35 ` Christian Brauner
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=20260219065014.3550402-2-hch@lst.de \
--to=hch@lst.de \
--cc=brauner@kernel.org \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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