From: Jaegeuk Kim <jaegeuk@kernel.org>
To: linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH 5/6 v2] f2fs-tools: use android config only if there's no config.h
Date: Tue, 26 Apr 2022 09:30:22 -0700 [thread overview]
Message-ID: <YmgeHgnGY2AFgjHl@google.com> (raw)
In-Reply-To: <20220422211819.2230879-5-jaegeuk@kernel.org>
Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
---
Change log from v1:
- Fix xfstests failure
include/f2fs_fs.h | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/include/f2fs_fs.h b/include/f2fs_fs.h
index d6374270c188..ad2798cf388c 100644
--- a/include/f2fs_fs.h
+++ b/include/f2fs_fs.h
@@ -26,13 +26,14 @@
#include <stddef.h>
#include <string.h>
#include <time.h>
+
#ifdef HAVE_CONFIG_H
#include <config.h>
-#endif
-
+#else
#ifdef __ANDROID__
#define WITH_ANDROID
#endif
+#endif /* HAVE_CONFIG_H */
#ifdef WITH_ANDROID
#include <android_config.h>
--
2.36.0.rc2.479.g8af0fa9b8e-goog
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next prev parent reply other threads:[~2022-04-26 16:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-22 21:18 [f2fs-dev] [PATCH 1/6] libf2fs_io: add unused mactor to avoid build failure Jaegeuk Kim
2022-04-22 21:18 ` [f2fs-dev] [PATCH 2/6] android_config.h: add missing liblz4 Jaegeuk Kim
2022-04-22 21:18 ` [f2fs-dev] [PATCH 3/6] f2fs-tools: support zoned device in Android Jaegeuk Kim
2022-04-26 23:06 ` [f2fs-dev] [PATCH 3/6 v2] " Jaegeuk Kim
2022-04-22 21:18 ` [f2fs-dev] [PATCH 4/6] f2fs-tools: use fsync() " Jaegeuk Kim
2022-04-22 21:18 ` [f2fs-dev] [PATCH 5/6] f2fs-tools: use android config only if there's no config.h Jaegeuk Kim
2022-04-26 16:30 ` Jaegeuk Kim [this message]
2022-04-22 21:18 ` [f2fs-dev] [PATCH 6/6] mkfs.f2fs: check uuid library Jaegeuk Kim
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=YmgeHgnGY2AFgjHl@google.com \
--to=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
/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.