linux-kernel - RE: [PATCH v2] Fix a build error when BLOCK=n

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 23 Oct 2007 12:27:26 -0700
From:	"Medve Emilian-EMMEDVE1" <Emilian.Medve@...escale.com>
To:	"Jens Axboe" <jens.axboe@...cle.com>
Cc:	<linux-kernel@...r.kernel.org>, <linux-mm@...ck.org>,
	<torvalds@...ux-foundation.org>
Subject: RE: [PATCH v2] Fix a build error when BLOCK=n

Hello Jens,


In who's tree would this go?


Thanks,
Emil.


> -----Original Message-----
> From: Jens Axboe [mailto:jens.axboe@...cle.com] 
> Sent: Thursday, October 18, 2007 10:27 AM
> To: Medve Emilian-EMMEDVE1
> Cc: linux-kernel@...r.kernel.org; linux-mm@...ck.org; 
> torvalds@...ux-foundation.org
> Subject: 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 <Emilian.Medve@...escale.com>
> 
> Acked-by: Jens Axboe <jens.axboe@...cle.com>
> 
> -- 
> Jens Axboe
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/