All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Ian Kent <raven@themaw.net>, "H. Peter Anvin" <hpa@zytor.com>,
	linux-kernel@vger.kernel.org, autofs@linux.kernel.org
Subject: Re: [PATCH 04/12] BKL: Remove BKL from autofs4
Date: Fri, 17 Sep 2010 10:01:33 -0700	[thread overview]
Message-ID: <20100917170133.GA13570@kroah.com> (raw)
In-Reply-To: <201009170917.29522.arnd@arndb.de>

On Fri, Sep 17, 2010 at 09:17:29AM +0200, Arnd Bergmann wrote:
> On Friday 17 September 2010 03:33:11 Ian Kent wrote:
> > On Thu, 2010-09-16 at 19:55 +0200, Arnd Bergmann wrote:
> > > Ah, sorry about this. I looked at the wrong MAINTAINERS entry.
> > > 
> > > I also forgot to Cc you about autofs3, adding more to the confusion. ;)
> > > 
> > > Do you think the time has come to move autofs3 to drivers/staging
> > > as we deprecate the BKL?
> > 
> > Umm ... what's this process, the drivers/staging?
> 
> We use drivers/staging now both for getting code into the kernel
> and for getting it out of there. Moving autofs3 to drivers/staging/autofs/
> would serve as a last warning to everyone using it, but users could
> still use it while it's there. If anyone is interested, they can submit
> fixes (BKL removal and whatever else is needed) to get it back into
> the mainline. If it doesn't happen, Greg would finally remove it two
> kernel releases later.
> 
> My hope is that we can move all modules that still use the BKL after
> 2.6.37 to drivers/staging, unless we have someone already working
> on the patches.

That sounds fine with me, send me patches whenever you want to and I
will gladly take them.

thanks,

greg k-h

  reply	other threads:[~2010-09-17 17:01 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-16 17:46 [PATCH 00/12] more BKL removal after get_sb pushdown Arnd Bergmann
2010-09-16 17:46 ` [PATCH 01/12] BKL: Remove BKL from usbfs Arnd Bergmann
2010-09-16 18:47   ` Greg KH
2010-09-16 17:46 ` [PATCH 02/12] BKL: Remove BKL from fat Arnd Bergmann
2010-09-16 17:46 ` [PATCH 03/12] BKL: Remove BKL from isofs Arnd Bergmann
2010-09-16 17:46 ` [PATCH 04/12] BKL: Remove BKL from autofs4 Arnd Bergmann
2010-09-16 17:49   ` H. Peter Anvin
2010-09-16 17:55     ` Arnd Bergmann
2010-09-16 19:20       ` H. Peter Anvin
2010-09-17  1:31         ` Ian Kent
2010-09-17  1:33       ` Ian Kent
2010-09-17  7:17         ` Arnd Bergmann
2010-09-17 17:01           ` Greg KH [this message]
2010-09-16 17:46 ` [PATCH 05/12] BKL: Remove BKL from ReiserFS Arnd Bergmann
2010-09-16 17:46 ` [PATCH 06/12] BKL: Remove BKL from capifs Arnd Bergmann
2010-09-17 23:35   ` David Miller
2010-09-18  7:55     ` Arnd Bergmann
2010-09-16 17:46 ` [PATCH 07/12] BKL: Remove BKL from USB gadgetfs Arnd Bergmann
2010-09-16 17:46 ` [PATCH 08/12] BKL: Remove BKL from afs Arnd Bergmann
2010-09-16 17:46 ` [PATCH 09/12] BKL: Remove BKL from ecryptfs Arnd Bergmann
2010-09-16 17:46 ` [PATCH 10/12] BKL: Remove BKL from jffs2 Arnd Bergmann
2010-09-16 17:46 ` [PATCH 11/12] BKL: Remove BKL from squashfs Arnd Bergmann
2010-09-16 17:46 ` [PATCH 12/12] BKL: Remove BKL from OCFS2 Arnd Bergmann
2010-09-16 22:26   ` Mark Fasheh

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=20100917170133.GA13570@kroah.com \
    --to=greg@kroah.com \
    --cc=arnd@arndb.de \
    --cc=autofs@linux.kernel.org \
    --cc=hpa@zytor.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.