From: Tim Pepper <lnxninja@linux.vnet.ibm.com>
To: linux-kernel@vger.kernel.org
Cc: linux-mm@kvack.org
Subject: [PATCH] mm: fix filemap.c's comment re: buffer_head.h inclusion reason
Date: Thu, 22 May 2008 16:54:27 -0700 [thread overview]
Message-ID: <20080522235426.GA28518@tpepper-t42p.dolavim.us> (raw)
It appears mm/filemap.c's comment on why buffer_head.h is included has
gotten out of date. Today generic_osync_inode() is coming from the fs.h
include and buffer_head.h is providing try_to_free_buffers().
Signed-off-by: Tim Pepper <lnxninja@linux.vnet.ibm.com>
Cc: linux-mm@kvack.org
---
diff --git a/mm/filemap.c b/mm/filemap.c
index 1e6a7d3..fe4adf4 100644
--- a/mm/filemap.c
+++ b/mm/filemap.c
@@ -38,7 +38,7 @@
/*
* FIXME: remove all knowledge of the buffer layer from the core VM
*/
-#include <linux/buffer_head.h> /* for generic_osync_inode */
+#include <linux/buffer_head.h> /* for try_to_free_buffers */
#include <asm/mman.h>
--
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>
reply other threads:[~2008-05-22 23:56 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=20080522235426.GA28518@tpepper-t42p.dolavim.us \
--to=lnxninja@linux.vnet.ibm.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