From: "H. Peter Anvin" <hpa@zytor.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: gregkh@suse.de, autofs@linux.kernel.org,
Ian Kent <raven@themaw.net>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH, RFC] autofs3: move to drivers/staging
Date: Mon, 04 Oct 2010 13:34:49 -0700 [thread overview]
Message-ID: <4CAA3A69.9040709@zytor.com> (raw)
In-Reply-To: <201010042228.10642.arnd@arndb.de>
On 10/04/2010 01:28 PM, Arnd Bergmann wrote:
> Nobody appears to be interested in fixing autofs3 bugs
> any more and it uses the BKL, which is going away.
>
> Move this to staging for retirement. Unless someone
> complains until 2.6.38, we can remove it for good.
>
> The include/linux/auto_fs.h header file is still used
> by autofs4, so it remains in place.
I say we should just delete it.
-hpa
next prev parent reply other threads:[~2010-10-04 20:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-04 20:28 [PATCH, RFC] autofs3: move to drivers/staging Arnd Bergmann
2010-10-04 20:34 ` H. Peter Anvin [this message]
2010-10-04 20:40 ` Greg KH
2010-10-04 21:05 ` H. Peter Anvin
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=4CAA3A69.9040709@zytor.com \
--to=hpa@zytor.com \
--cc=arnd@arndb.de \
--cc=autofs@linux.kernel.org \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=raven@themaw.net \
/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