From: Andrew Morton <akpm@osdl.org>
To: Ian Kent <raven@themaw.net>
Cc: hch@infradead.org, viro@parcelfarce.linux.theplanet.co.uk,
linux-kernel@vger.kernel.org
Subject: Re: 2.6.6-rc1-mm1
Date: Mon, 19 Apr 2004 18:26:57 -0700 [thread overview]
Message-ID: <20040419182657.7870aee9.akpm@osdl.org> (raw)
In-Reply-To: <Pine.LNX.4.58.0404200911090.12229@wombat.indigo.net.au>
Ian Kent <raven@themaw.net> wrote:
>
> On Mon, 19 Apr 2004, Christoph Hellwig wrote:
>
> > 4-autofs4-2.6.0-expire-20040405.patch exports vfsmount_lock which is probably
> > not exactly a good design. It's only used by autofs4_may_umount which isn't
> > autofs-specific at all.
> >
>
> Sorry Christoph, your recommendation is?
>
May as well rename that function to may_umount(), document it, suck it into
fs/namespace.c or fs/namei.c and export it to modules.
That does increase the size of the static kernel a little, so arguably we
shouldn't make this change until/unless we see a second user of the
function.
next prev parent reply other threads:[~2004-04-20 1:27 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-19 6:01 2.6.6-rc1-mm1 Andrew Morton
2004-04-19 6:29 ` 2.6.6-rc1-mm1 William Lee Irwin III
2004-04-19 6:42 ` 2.6.6-rc1-mm1 Andrew Morton
2004-04-19 6:49 ` 2.6.6-rc1-mm1 William Lee Irwin III
2004-04-19 7:06 ` 2.6.6-rc1-mm1 William Lee Irwin III
2004-04-19 18:39 ` bitmap, cpumask_arith (was: 2.6.6-rc1-mm1) Paul Jackson
2004-04-20 21:17 ` Paul Jackson
2004-04-20 21:38 ` William Lee Irwin III
2004-04-19 6:58 ` 2.6.6-rc1-mm1 Nick Piggin
2004-04-19 9:13 ` 2.6.6-rc1-mm1 failure: kmod.o didn't compile with module-less setup Helge Hafting
2004-04-19 9:17 ` Andrew Morton
2004-04-19 15:26 ` 2.6.6-rc1-mm1 (compile stats) John Cherry
2004-04-19 19:25 ` 2.6.6-rc1-mm1 Christoph Hellwig
2004-04-20 1:13 ` 2.6.6-rc1-mm1 Ian Kent
2004-04-20 1:26 ` Andrew Morton [this message]
2004-04-21 9:08 ` 2.6.6-rc1-mm1 Christoph Hellwig
2004-04-21 12:31 ` 2.6.6-rc1-mm1 raven
2004-04-21 13:18 ` 2.6.6-rc1-mm1 Christoph Hellwig
2004-04-21 13:34 ` 2.6.6-rc1-mm1 raven
2004-04-21 15:52 ` 2.6.6-rc1-mm1 raven
2004-04-21 16:09 ` 2.6.6-rc1-mm1 Christoph Hellwig
2004-04-21 12:39 ` 2.6.6-rc1-mm1 raven
2004-04-21 13:19 ` 2.6.6-rc1-mm1 Christoph Hellwig
2004-04-21 13:52 ` 2.6.6-rc1-mm1 raven
2004-04-21 14:56 ` 2.6.6-rc1-mm1 Christoph Hellwig
2004-04-21 15:39 ` 2.6.6-rc1-mm1 raven
2004-04-20 14:27 ` 2.6.6-rc1-mm1 raven
2004-04-20 15:06 ` 2.6.6-rc1-mm1 Rik van Riel
2004-04-21 7:37 ` 2.6.6-rc1-mm1 Sean Neakums
2004-04-21 12:16 ` 2.6.6-rc1-mm1 Hugh Dickins
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=20040419182657.7870aee9.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=raven@themaw.net \
--cc=viro@parcelfarce.linux.theplanet.co.uk \
/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
all inboxes | Powered by JetHome®