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>,
Thomas Gleixner <tglx@linutronix.de>,
John Kacur <jkacur@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: [GIT PULL] bkl ioctl pushdowns for 2.6.36
Date: Mon, 9 Aug 2010 06:19:32 +0200 [thread overview]
Message-ID: <1281327572-411-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
There is a merge of a recent version of your master branch inside. This
is because we would like to remove the struct file_operations:ioctl callback
by the end of this merge window. But we missed the new easycap driver
that got merged in staging and which is one of the last that uses the ioctl
callback.
Usually we would have prefered this pushdown to go through the staging
tree but since I don't know if there will be another staging merge for
this -rc1, I have merged your tree that has this driver and did the
pushdown in my branch.
The rest of the pending bkl ioctl pushdowns are in the
logfs and ecryptfs trees. If everything goes well, we'll propose
a patch to remove ioctl by the end of the merge window.
Thanks,
Frederic
---
Arnd Bergmann (3):
ia64/perfmon: Convert to unlocked_ioctl
v4l: Convert v4l2-dev to unlocked_ioctl
autofs/autofs4: Move compat_ioctl handling into fs
Frederic Weisbecker (1):
staging: Pushdown bkl to easycap ioctl handlers
Huang Weiyi (2):
ncpfs: Remove duplicated #include
sunrpc: Remove duplicated #include
drivers/media/video/v4l2-dev.c | 52 +++++++-----------------
drivers/staging/easycap/easycap.h | 8 +---
drivers/staging/easycap/easycap_ioctl.c | 52 ++++++++++++++----------
drivers/staging/easycap/easycap_main.c | 38 +++++++++---------
fs/autofs/root.c | 67 +++++++++++++++++++++++++++++-
fs/autofs4/root.c | 49 ++++++++++++++++++++++
fs/compat_ioctl.c | 36 ----------------
fs/ncpfs/ioctl.c | 1 -
include/linux/auto_fs.h | 1 +
9 files changed, 180 insertions(+), 124 deletions(-)
reply other threads:[~2010-08-09 4:19 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=1281327572-411-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=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
/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).