From: Emil Medve <Emilian.Medve@Freescale.com>
To: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
torvalds@linux-foundation.org, jens.axboe@oracle.com
Cc: Emil Medve <Emilian.Medve@Freescale.com>
Subject: [PATCH v2] Fix a build error when BLOCK=n
Date: Thu, 18 Oct 2007 09:55:29 -0500 [thread overview]
Message-ID: <1192719329-32066-1-git-send-email-Emilian.Medve@Freescale.com> (raw)
This happens when we don't use/have any block devices and a NFS root filesystem
is used
mapping_cap_writeback_dirty() is defined in linux/backing-dev.h which used to be
provided in mm/filemap.c by linux/blkdev.h until commit
f5ff8422bbdd59f8c1f699df248e1b7a11073027
Signed-off-by: Emil Medve <Emilian.Medve@Freescale.com>
---
This is against Linus' tree: d85714d81cc0408daddb68c10f7fd69eafe7c213
linux-2.6> scripts/checkpatch.pl 0001-Fix-a-build-error-when-BLOCK-n.patch
Your patch has no obvious style problems and is ready for submission.
mm/filemap.c | 1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/mm/filemap.c b/mm/filemap.c
index 79f24a9..61efe94 100644
--- a/mm/filemap.c
+++ b/mm/filemap.c
@@ -27,6 +27,7 @@
#include <linux/writeback.h>
#include <linux/pagevec.h>
#include <linux/blkdev.h>
+#include <linux/backing-dev.h>
#include <linux/security.h>
#include <linux/syscalls.h>
#include <linux/cpuset.h>
--
1.5.3.GIT
--
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/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next reply other threads:[~2007-10-18 14:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-18 14:55 Emil Medve [this message]
2007-10-18 15:26 ` Jens Axboe
2007-10-23 19:27 ` Medve Emilian-EMMEDVE1
2007-10-23 20:21 ` Jens Axboe
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=1192719329-32066-1-git-send-email-Emilian.Medve@Freescale.com \
--to=emilian.medve@freescale.com \
--cc=jens.axboe@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=torvalds@linux-foundation.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