public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Frederic Weisbecker <fweisbec@gmail.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Arnd Bergmann <arnd@arndb.de>,
	linux-kernel@vger.kernel.org, John Kacur <jkacur@redhat.com>,
	Al Viro <viro@zeniv.linux.org.uk>, Ian Kent <raven@themaw.net>,
	autofs@linux.kernel.org
Subject: Re: [PATCH 3/6] autofs/autofs4: move compat_ioctl handling into fs
Date: Mon, 5 Jul 2010 21:48:01 +0200	[thread overview]
Message-ID: <20100705194759.GE5240@nowhere> (raw)
In-Reply-To: <4C3235C3.7050303@zytor.com>

On Mon, Jul 05, 2010 at 12:42:59PM -0700, H. Peter Anvin wrote:
> On 07/05/2010 12:24 PM, Frederic Weisbecker wrote:
> > On Sun, Jul 04, 2010 at 12:15:07AM +0200, Arnd Bergmann wrote:
> >> Handling of autofs ioctl numbers does not need to be generic
> >> and can easily be done directly in autofs itself.
> >>
> >> This also pushes the BKL into autofs and autofs4 ioctl
> >> methods.
> >>
> >> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
> >> Cc: H. Peter Anvin <hpa@zytor.com>
> > 
> > Peter, if you're fine with this version. May I apply it?
> > Unless you have a tree for autofs.
> > 
> > Thanks.
> 
> Ian Kent is the maintainer of autofs4 and patches for autofs4 should go
> through him (or acked by him.)
> 
> autofs 3 is officially unmaintained; I'm more than happy to have you
> push the autofs 3 bits of this patch.


Sure, I can split up the patch and integrate the autofs 3 part, I'll send
the standalone autofs4 version to Ian.

Thanks.


  reply	other threads:[~2010-07-05 19:47 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-03 22:15 [PATCH 0/6] kill .ioctl file_operation Arnd Bergmann
2010-07-03 22:15 ` [PATCH 1/6] ia64/perfmon: convert to unlocked_ioctl Arnd Bergmann
2010-07-21 23:16   ` Frederic Weisbecker
2010-07-03 22:15 ` [PATCH 2/6] sound/oss: " Arnd Bergmann
2010-07-04 11:08   ` Sam Ravnborg
2010-07-04 20:52     ` Arnd Bergmann
2010-07-03 22:15 ` [PATCH 3/6] autofs/autofs4: move compat_ioctl handling into fs Arnd Bergmann
2010-07-05 19:24   ` Frederic Weisbecker
2010-07-05 19:42     ` H. Peter Anvin
2010-07-05 19:48       ` Frederic Weisbecker [this message]
2010-07-05 19:52         ` Arnd Bergmann
2010-07-05 19:58           ` Frederic Weisbecker
2010-07-05 20:12             ` H. Peter Anvin
2010-07-06  1:11             ` Ian Kent
2010-07-06 11:35               ` Arnd Bergmann
2010-07-06 13:17                 ` Ian Kent
2010-07-16  0:14                   ` Frederic Weisbecker
2010-07-16  4:40                     ` Ian Kent
2010-07-16 11:05                       ` Arnd Bergmann
2010-07-16 12:09                         ` Frederic Weisbecker
2010-07-03 22:15 ` [PATCH 4/6] cris: Pushdown the bkl from ioctl Arnd Bergmann
2010-07-30 17:08   ` Jesper Nilsson
2010-07-03 22:15 ` [PATCH 5/6] v4l: convert v4l2-dev to unlocked_ioctl Arnd Bergmann
2010-07-05 19:27   ` Frederic Weisbecker
2010-07-03 22:15 ` [PATCH 6/6] bkl: remove locked .ioctl file operation Arnd Bergmann

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=20100705194759.GE5240@nowhere \
    --to=fweisbec@gmail.com \
    --cc=arnd@arndb.de \
    --cc=autofs@linux.kernel.org \
    --cc=hpa@zytor.com \
    --cc=jkacur@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=raven@themaw.net \
    --cc=viro@zeniv.linux.org.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