Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1764012AbXJRPFJ (ORCPT ); Thu, 18 Oct 2007 11:05:09 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1756207AbXJRPE6 (ORCPT ); Thu, 18 Oct 2007 11:04:58 -0400 Received: from az33egw01.freescale.net ([192.88.158.102]:47669 "EHLO az33egw01.freescale.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753620AbXJRPE6 (ORCPT ); Thu, 18 Oct 2007 11:04:58 -0400 From: Emil Medve To: linux-kernel@vger.kernel.org, linux-mm@kvack.org, torvalds@linux-foundation.org, jens.axboe@oracle.com Cc: Emil Medve Subject: [PATCH v2] Fix a build error when BLOCK=n Date: Thu, 18 Oct 2007 09:55:29 -0500 Message-Id: <1192719329-32066-1-git-send-email-Emilian.Medve@Freescale.com> X-Mailer: git-send-email 1.5.3.GIT X-Brightmail-Tracker: AAAAAQAAAAQ= X-Whitelist: TRUE Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1354 Lines: 41 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 --- This is against Linus' tree: d85714d81cc0408daddb68c10f7fd69eafe7c213 linux-2.6> scripts/checkpatch.pl 0001-Fix-a-build-error-when-BLOCK-n.patch Your patch has no obvious style problems and is ready for submission. mm/filemap.c | 1 + 1 files changed, 1 insertions(+), 0 deletions(-) diff --git a/mm/filemap.c b/mm/filemap.c index 79f24a9..61efe94 100644 --- a/mm/filemap.c +++ b/mm/filemap.c @@ -27,6 +27,7 @@ #include #include #include +#include #include #include #include -- 1.5.3.GIT - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/