From: Jaegeuk Kim <jaegeuk@kernel.org>
To: linux-f2fs-devel@lists.sourceforge.net
Cc: Tom Cherry <tomcherry@google.com>, Jaegeuk Kim <jaegeuk@kernel.org>
Subject: [f2fs-dev] [PATCH] Include private/fs_config.h directly when needed
Date: Thu, 5 Mar 2020 19:37:41 -0800 [thread overview]
Message-ID: <20200306033741.113980-1-jaegeuk@kernel.org> (raw)
From: Tom Cherry <tomcherry@google.com>
This is no longer a transitive include of android_filesystem_config.h
Signed-off-by: Tom Cherry <tomcherry@google.com>
Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
---
fsck/sload.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/fsck/sload.c b/fsck/sload.c
index f601916..c064f7f 100644
--- a/fsck/sload.c
+++ b/fsck/sload.c
@@ -34,6 +34,7 @@ static fs_config_f fs_config_func = NULL;
#include <selinux/android.h>
#include <private/android_filesystem_config.h>
#include <private/canned_fs_config.h>
+#include <private/fs_config.h>
#endif
static int filter_dot(const struct dirent *d)
--
2.25.1.481.gfbce0eb801-goog
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next reply other threads:[~2020-03-06 3:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-06 3:37 Jaegeuk Kim [this message]
2020-03-16 2:59 ` [f2fs-dev] [PATCH] Include private/fs_config.h directly when needed Chao Yu
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=20200306033741.113980-1-jaegeuk@kernel.org \
--to=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=tomcherry@google.com \
/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).