From: Jaegeuk Kim <jaegeuk@kernel.org>
To: linux-f2fs-devel@lists.sourceforge.net
Cc: Jaegeuk Kim <jaegeuk@kernel.org>
Subject: [f2fs-dev] [PATCH 4/6] f2fs-tools: use fsync() in Android
Date: Fri, 22 Apr 2022 14:18:17 -0700 [thread overview]
Message-ID: <20220422211819.2230879-4-jaegeuk@kernel.org> (raw)
In-Reply-To: <20220422211819.2230879-1-jaegeuk@kernel.org>
Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
---
include/android_config.h | 1 +
1 file changed, 1 insertion(+)
diff --git a/include/android_config.h b/include/android_config.h
index 671cab6fb003..5a856a30fd8c 100644
--- a/include/android_config.h
+++ b/include/android_config.h
@@ -3,6 +3,7 @@
#define HAVE_BYTESWAP_H 1
#define HAVE_FCNTL_H 1
#define HAVE_FALLOC_H 1
+#define HAVE_FSYNC 1
#define HAVE_KERNEL_UAPI_LINUX_BLKZONED_H 1
#define HAVE_LINUX_HDREG_H 1
#define HAVE_LINUX_LIMITS_H 1
--
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-22 21:18 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 ` Jaegeuk Kim [this message]
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 ` [f2fs-dev] [PATCH 5/6 v2] " Jaegeuk Kim
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=20220422211819.2230879-4-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 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.