Re: [PATCH v2] Fix a build error when BLOCK=n

On Thu, Oct 18 2007, Emil Medve wrote:
> mm/filemap.c: In function '__filemap_fdatawrite_range':
> mm/filemap.c:200: error: implicit declaration of function 'mapping_cap_writeback_dirty'
> 
> 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 <[email protected]>

Acked-by: Jens Axboe <[email protected]>

-- 
Jens Axboe

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Follow-Ups:
- RE: [PATCH v2] Fix a build error when BLOCK=n
  - From: "Medve Emilian-EMMEDVE1" <[email protected]>

References:
- [PATCH v2] Fix a build error when BLOCK=n
  - From: Emil Medve <[email protected]>

Prev by Date: [PATCH] Kconfig: Missing line breaks in arch/x86_64/Kconfig
Next by Date: Re: [RFC] [PATCH 2/2] capabilities: implement 64-bit capabilities
Previous by thread: [PATCH v2] Fix a build error when BLOCK=n
Next by thread: RE: [PATCH v2] Fix a build error when BLOCK=n
Index(es):
- Date
- Thread

[Index of Archives] [Kernel Newbies] [Netfilter] [Bugtraq] [Photo] [Stuff] [Gimp] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Video 4 Linux] [Linux for the blind] [Linux Resources]