From: Jaegeuk Kim <jaegeuk@kernel.org>
To: linux-f2fs-devel@lists.sourceforge.net
Cc: Jaegeuk Kim <jaegeuk@kernel.org>
Subject: [PATCH] f2fs-tools: define WITH_ANDROID if __ANDROID__ is defined
Date: Thu, 16 Nov 2017 16:26:50 -0800 [thread overview]
Message-ID: <20171117002650.97118-1-jaegeuk@kernel.org> (raw)
This matches with __ANDROID__ with WITH_ANDROID.
Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
---
include/f2fs_fs.h | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/include/f2fs_fs.h b/include/f2fs_fs.h
index 05b893a..7221844 100644
--- a/include/f2fs_fs.h
+++ b/include/f2fs_fs.h
@@ -16,6 +16,10 @@
#include <config.h>
#endif
+#ifdef __ANDROID__
+#define WITH_ANDROID
+#endif
+
#ifdef WITH_ANDROID
#include <android_config.h>
#endif
--
2.14.0.rc1.383.gd1ce394fe2-goog
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
reply other threads:[~2017-11-17 0:26 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20171117002650.97118-1-jaegeuk@kernel.org \
--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 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).