From: "Medve Emilian-EMMEDVE1" <Emilian.Medve@freescale.com>
To: Jens Axboe <jens.axboe@oracle.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
torvalds@linux-foundation.org
Subject: RE: [PATCH v2] Fix a build error when BLOCK=n
Date: Tue, 23 Oct 2007 12:27:26 -0700 [thread overview]
Message-ID: <598D5675D34BE349929AF5EDE9B03E27016E5644@az33exm24.fsl.freescale.net> (raw)
In-Reply-To: <20071018152645.GC10674@kernel.dk>
Hello Jens,
In who's tree would this go?
Thanks,
Emil.
> -----Original Message-----
> From: Jens Axboe [mailto:jens.axboe@oracle.com]
> Sent: Thursday, October 18, 2007 10:27 AM
> To: Medve Emilian-EMMEDVE1
> Cc: linux-kernel@vger.kernel.org; linux-mm@kvack.org;
> torvalds@linux-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@Freescale.com>
>
> Acked-by: Jens Axboe <jens.axboe@oracle.com>
>
> --
> Jens Axboe
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2007-10-23 19:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-18 14:55 Emil Medve
2007-10-18 15:26 ` Jens Axboe
2007-10-23 19:27 ` Medve Emilian-EMMEDVE1 [this message]
2007-10-23 20:21 ` Jens Axboe
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=598D5675D34BE349929AF5EDE9B03E27016E5644@az33exm24.fsl.freescale.net \
--to=emilian.medve@freescale.com \
--cc=jens.axboe@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=torvalds@linux-foundation.org \
/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