From: Kautuk Consul <consul.kautuk@gmail.com>
To: Hugh Dickins <hughd@google.com>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Kautuk Consul <consul.kautuk@gmail.com>
Subject: [PATCH 1/1] shmem.c: Compilation failure in shmem_file_setup for !CONFIG_MMU
Date: Mon, 20 Feb 2012 06:11:32 -0500 [thread overview]
Message-ID: <1329736292-19087-1-git-send-email-consul.kautuk@gmail.com> (raw)
I disabled the CONFIG_MMU and tried to compile the kernel and got the
following problem:
In function a??shmem_file_setupa??:
error: implicit declaration of function a??ramfs_nommu_expand_for_mappinga??
This is because, we do not include ramfs.h for CONFIG_SHMEM.
Included linux/ramfs.h for both CONFIG_SHMEM as well as !CONFIG_SHMEM.
Signed-off-by: Kautuk Consul <consul.kautuk@gmail.com>
---
mm/shmem.c | 3 +--
1 files changed, 1 insertions(+), 2 deletions(-)
diff --git a/mm/shmem.c b/mm/shmem.c
index 269d049..4884188 100644
--- a/mm/shmem.c
+++ b/mm/shmem.c
@@ -30,6 +30,7 @@
#include <linux/mm.h>
#include <linux/export.h>
#include <linux/swap.h>
+#include <linux/ramfs.h>
static struct vfsmount *shm_mnt;
@@ -2442,8 +2443,6 @@ out4:
* effectively equivalent, but much lighter weight.
*/
-#include <linux/ramfs.h>
-
static struct file_system_type shmem_fs_type = {
.name = "tmpfs",
.mount = ramfs_mount,
--
1.7.5.4
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next reply other threads:[~2012-02-20 11:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-20 11:11 Kautuk Consul [this message]
2012-02-20 19:29 ` [PATCH 1/1] shmem.c: Compilation failure in shmem_file_setup for !CONFIG_MMU Hugh Dickins
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=1329736292-19087-1-git-send-email-consul.kautuk@gmail.com \
--to=consul.kautuk@gmail.com \
--cc=hughd@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
/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).