linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@xenotime.net>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
	Linus <torvalds@linux-foundation.org>,
	Al Viro <viro@ZenIV.linux.org.uk>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: [PATCH -next] fs: fix fs/fs-writeback.c build error
Date: Thu, 05 Jan 2012 16:18:30 -0800	[thread overview]
Message-ID: <4F063DD6.5050403@xenotime.net> (raw)
In-Reply-To: <20120105191218.42825638a431bc1aba4879de@canb.auug.org.au>

From: Randy Dunlap <rdunlap@xenotime.net>

In linux-next, fs/fs-writeback.c no longer #includes <linux/buffer_head.h>,
which #included <linux/pagemap.h>, so add that latter header file to
<linux/writeback.h> to fix the build error:

fs/fs-writeback.c:510:11: error: 'PAGE_CACHE_SHIFT' undeclared (first use in this function)

Signed-off-by: Randy Dunlap <rdunlap@xenotime.net>
---
 include/linux/writeback.h |    1 +
 1 file changed, 1 insertion(+)

--- linux-next-20120105.orig/include/linux/writeback.h
+++ linux-next-20120105/include/linux/writeback.h
@@ -6,6 +6,7 @@
 
 #include <linux/sched.h>
 #include <linux/fs.h>
+#include <linux/pagemap.h>
 
 DECLARE_PER_CPU(int, dirty_throttle_leaks);
 

  reply	other threads:[~2012-01-06 22:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-05  8:12 linux-next: Tree for Jan 5 Stephen Rothwell
2012-01-06  0:18 ` Randy Dunlap [this message]
2012-01-06 23:01   ` [PATCH -next] fs: fix fs/fs-writeback.c build error Linus Torvalds
2012-01-07 13:30     ` Wu Fengguang
2012-01-07 18:17       ` Randy Dunlap
2012-01-06  0:48 ` linux-next: Tree for Jan 5 (exofs or nfs ?) Randy Dunlap
     [not found]   ` <4F0644C1.6000405-/UHa2rfvQTnk1uMJSBkQmQ@public.gmane.org>
2012-01-08  8:36     ` Boaz Harrosh

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=4F063DD6.5050403@xenotime.net \
    --to=rdunlap@xenotime.net \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=torvalds@linux-foundation.org \
    --cc=viro@ZenIV.linux.org.uk \
    /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).