linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@xenotime.net>
To: "Toralf Förster" <toralf.foerster@gmx.de>
Cc: viro@zeniv.linux.org.uk, linux-fsdevel@vger.kernel.org,
	Wu Fengguang <fengguang.wu@intel.com>
Subject: Re: Fwd: build issue #4 for v3.2-3495-ga0e86bd :fs/fs-writeback.c:510:11: error: PAGE_CACHE_SHIFT undeclared
Date: Mon, 09 Jan 2012 09:30:50 -0800	[thread overview]
Message-ID: <4F0B244A.2080805@xenotime.net> (raw)
In-Reply-To: <201201091017.40926.toralf.foerster@gmx.de>

On 01/09/2012 01:17 AM, Toralf Förster wrote:
> 
> Hello,
> 
> the build (.config attached) failed, make ends with :
> ...
>   CC      fs/fs-writeback.o
> fs/fs-writeback.c: In function ‘writeback_chunk_size’:
> fs/fs-writeback.c:510:11: error: ‘PAGE_CACHE_SHIFT’ undeclared (first use 
> in this function)
> fs/fs-writeback.c:510:11: note: each undeclared identifier is reported only 
> once for each function it appears in
> fs/fs-writeback.c:510:3: warning: type defaults to ‘int’ in type name
> make[1]: *** [fs/fs-writeback.o] Error 1
> make: *** [fs] Error 2
> 
> The build was made with :
> $>make randconfig; make clean; make
> 
> Here's the config:

Patch was posted on Jan. 7, but was probably done for linux-next, not mainline.

See https://lkml.org/lkml/2012/1/7/70

-- 
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2012-01-09 16:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-09  9:17 Fwd: build issue #4 for v3.2-3495-ga0e86bd :fs/fs-writeback.c:510:11: error: PAGE_CACHE_SHIFT undeclared Toralf Förster
2012-01-09 17:30 ` Randy Dunlap [this message]
2012-01-10  8:27   ` Wu Fengguang

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=4F0B244A.2080805@xenotime.net \
    --to=rdunlap@xenotime.net \
    --cc=fengguang.wu@intel.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=toralf.foerster@gmx.de \
    --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).