From: Frederic Weisbecker <fweisbec@gmail.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
Arnd Bergmann <arnd@arndb.de>, John Kacur <jkacur@redhat.com>,
Al Viro <viro@ZenIV.linux.org.uk>,
Thomas Gleixner <tglx@linutronix.de>,
Mauro Carvalho Chehab <mchehab@redhat.com>,
Joern Engel <joern@logfs.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: [GIT PULL] Bkl ioctl removal for 2.6.36
Date: Sat, 14 Aug 2010 02:47:48 +0200 [thread overview]
Message-ID: <1281746868-6731-1-git-send-regression-fweisbec@gmail.com> (raw)
Linus,
Please pull the bkl/ioctl branch that can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/frederic/random-tracing.git
bkl/ioctl
This removes struct file_operations:ioctl() as there are no more users
of it.
That branch is based on a very recent version of your tree and not
2.6.35 because I needed every pending pushdowns to be upstream before
applying the final removal (and test it with allyesconfig).
Thanks,
Frederic
---
Arnd Bergmann (2):
logfs: kill BKL
bkl: Remove locked .ioctl file operation
Frederic Weisbecker (1):
v4l: Remove reference to bkl ioctl in compat ioctl handling
Documentation/filesystems/Locking | 8 +-------
Documentation/filesystems/vfs.txt | 6 +-----
drivers/media/video/v4l2-compat-ioctl32.c | 7 +------
fs/bad_inode.c | 7 -------
fs/compat_ioctl.c | 3 +--
fs/ioctl.c | 18 ++++--------------
fs/logfs/dir.c | 2 +-
fs/logfs/file.c | 6 +++---
fs/logfs/logfs.h | 3 +--
fs/proc/inode.c | 17 ++++-------------
include/linux/fs.h | 5 ++---
11 files changed, 19 insertions(+), 63 deletions(-)
reply other threads:[~2010-08-14 0:47 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1281746868-6731-1-git-send-regression-fweisbec@gmail.com \
--to=fweisbec@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=jkacur@redhat.com \
--cc=joern@logfs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@redhat.com \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--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;
as well as URLs for NNTP newsgroup(s).