From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Nick Piggin <npiggin@suse.de>,
hugh@veritas.com, Linux Memory Management <linux-mm@kvack.org>
Subject: Re: [RFC/PATCH] prepare_unmapped_area
Date: Tue, 06 Feb 2007 16:46:00 +1100 [thread overview]
Message-ID: <1170740760.2620.222.camel@localhost.localdomain> (raw)
In-Reply-To: <20070205213130.308a8c76.akpm@linux-foundation.org>
On Mon, 2007-02-05 at 21:31 -0800, Andrew Morton wrote:
> On Tue, 06 Feb 2007 16:04:56 +1100 Benjamin Herrenschmidt <benh@kernel.crashing.org> wrote:
>
> > +#ifndef HAVE_ARCH_PREPARE_UNMAPPED_AREA
> > +int arch_prepare_unmapped_area(struct file *file, unsigned long addr,
>
> __attribute__((weak)), please.
Not sure about that ... it will usually be inline, in fact, should be
static inline...
Ben.
--
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-02-06 5:46 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200702060405.l1645R7G009668@shell0.pdx.osdl.net>
[not found] ` <1170736938.2620.213.camel@localhost.localdomain>
[not found] ` <20070206044516.GA16647@wotan.suse.de>
2007-02-06 5:04 ` [RFC/PATCH] prepare_unmapped_area Benjamin Herrenschmidt
2007-02-06 5:31 ` Andrew Morton
2007-02-06 5:46 ` Benjamin Herrenschmidt [this message]
2007-02-06 5:58 ` Andrew Morton
2007-02-06 6:02 ` Benjamin Herrenschmidt
2007-02-06 6:08 ` Andrew Morton
2007-02-06 6:12 ` Nick Piggin
2007-02-06 6:37 ` Andrew Morton
2007-02-06 6:40 ` Nick Piggin
2007-02-06 6:54 ` Andrew Morton
2007-02-06 9:55 ` Christoph Hellwig
2007-02-06 10:07 ` Benjamin Herrenschmidt
2007-02-06 10:23 ` Christoph Hellwig
2007-02-06 15:56 ` Adam Litke
2007-02-06 20:12 ` Benjamin Herrenschmidt
2007-02-06 20:52 ` Adam Litke
2007-02-06 21:02 ` Benjamin Herrenschmidt
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=1170740760.2620.222.camel@localhost.localdomain \
--to=benh@kernel.crashing.org \
--cc=akpm@linux-foundation.org \
--cc=hugh@veritas.com \
--cc=linux-mm@kvack.org \
--cc=npiggin@suse.de \
/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).