From: Adrian Bunk <bunk@stusta.de>
To: Hugh Dickins <hugh@veritas.com>
Cc: Christoph Hellwig <hch@infradead.org>,
Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] unexport install_page
Date: Tue, 21 Feb 2006 15:13:41 +0100 [thread overview]
Message-ID: <20060221141341.GW4661@stusta.de> (raw)
In-Reply-To: <Pine.LNX.4.61.0602211227450.8400@goblin.wat.veritas.com>
On Tue, Feb 21, 2006 at 12:49:51PM +0000, Hugh Dickins wrote:
>...
> Why's that? It's rightly been recognized as a library function since
> 2.6.0-test3. I'd say it should remain exported for whatever filesystems
> might wish to use it (but no, I've no vested interest, the filesystem
> you'll suspect me of arguing for does not use it ;)
>
> <akpm@osdl.org>
> [PATCH] export install_page() to modules
>
> install_page() is a library function which we expect will be used by all
> drivers which implement vm_operations.populate(). Therefore it should be
> exported to kernel modules.
>
> Petr Vandrovec has a project which involves sparse mappings of device memory
> which can use remap_file_pages(). It needs install_page().
This export was justified in mid-2003 with a projet that would use it.
Now it's 2006, and there's still no in-kernel user.
This means it has only bloated the kernel for two and a half years
for nearly everyone.
> Hugh
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2006-02-21 14:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-20 22:37 [2.6 patch] unexport install_page Adrian Bunk
2006-02-21 10:38 ` Christoph Hellwig
2006-02-21 12:49 ` Hugh Dickins
2006-02-21 14:13 ` Adrian Bunk [this message]
2006-02-21 14:34 ` Alan Cox
2006-02-21 14:36 ` Adrian Bunk
-- strict thread matches above, loose matches on Subject: below --
2006-06-29 19:19 Adrian Bunk
2006-02-16 17:03 Adrian Bunk
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=20060221141341.GW4661@stusta.de \
--to=bunk@stusta.de \
--cc=akpm@osdl.org \
--cc=hch@infradead.org \
--cc=hugh@veritas.com \
--cc=linux-kernel@vger.kernel.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