From: John Kacur <jkacur@redhat.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Alan Cox <alan@linux.intel.com>, Arnd Bergmann <arnd@arndb.de>,
Andrew Morton <akpm@linux-foundation.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
Jan Blunck <jblunck@gmail.com>, Matthew Wilcox <matthew@wil.cx>,
Oleg Nesterov <oleg@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] nvram: Convert nvram_ioctl to unlocked_ioctl, remove smp_lock.h
Date: Mon, 29 Mar 2010 09:33:42 -0400 (EDT) [thread overview]
Message-ID: <1383519680.42441269869622199.JavaMail.root@zmail07.collab.prod.int.phx2.redhat.com> (raw)
In-Reply-To: <1269866171-7331-2-git-send-email-jkacur@redhat.com>
----- "John Kacur" <jkacur@redhat.com> wrote:
> After removing the BKL from open, we can also convert nvram_ioctl to
> an unlocked_ioctl. It has it's only spin_lock, and doesn't rely on the
> BKL
>
> This file no longer uses the BKL so smp_lock.h can be removed.
>
> Signed-off-by: John Kacur <jkacur@redhat.com>
> ---
> drivers/char/nvram.c | 18 ++++++++----------
> 1 files changed, 8 insertions(+), 10 deletions(-)
>
> diff --git a/drivers/char/nvram.c b/drivers/char/nvram.c
> index 5eb83c3..0c3ba6a 100644
> --- a/drivers/char/nvram.c
> +++ b/drivers/char/nvram.c
> @@ -110,7 +110,6 @@
> #include <linux/spinlock.h>
> #include <linux/io.h>
> #include <linux/uaccess.h>
> -#include <linux/smp_lock.h>
>
> #include <asm/system.h>
>
> @@ -297,8 +296,7 @@ checksum_err:
> return -EIO;
> }
>
> -static int nvram_ioctl(struct inode *inode, struct file *file,
> - unsigned int cmd, unsigned long arg)
> +static long nvram_ioctl(struct file *file, unsigned int cmd, unsigned
> long arg)
> {
> int i;
>
> @@ -419,13 +417,13 @@ static int nvram_add_proc_fs(void)
> #endif /* CONFIG_PROC_FS */
>
> static const struct file_operations nvram_fops = {
> - .owner = THIS_MODULE,
> - .llseek = nvram_llseek,
> - .read = nvram_read,
> - .write = nvram_write,
> - .ioctl = nvram_ioctl,
> - .open = nvram_open,
> - .release = nvram_release,
> + .owner = THIS_MODULE,
> + .llseek = nvram_llseek,
> + .read = nvram_read,
> + .write = nvram_write,
> + .unlocked_ioctl = nvram_ioctl,
> + .open = nvram_open,
> + .release = nvram_release,
> };
>
> static struct miscdevice nvram_dev = {
> --
> 1.6.0.6
Sorry for the double send, I must have messed-up something with
git-send-email. The --compose failed on me, and that part of the message was
lost afaict.
What I wanted to say was, Ingo, in the past you carried nvram fixes, so
if no-one objects to this change, can you integrate this one?
This did have a curiosity in the history. It seems that Linus's tree had the
remove smp_lock.h patch before the patch to remove BKL hit his tree. So
I combined that little bit with my previous patch that turns this into
an unlocked ioctl. (resend of http://lkml.indiana.edu/hypermail/linux/kernel/0910.2/01608.html)
Thanks
John
next parent reply other threads:[~2010-03-29 13:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1269866171-7331-2-git-send-email-jkacur@redhat.com>
2010-03-29 13:33 ` John Kacur [this message]
2010-03-29 18:56 ` Frederic Weisbecker
2010-03-29 19:06 ` John Kacur
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=1383519680.42441269869622199.JavaMail.root@zmail07.collab.prod.int.phx2.redhat.com \
--to=jkacur@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=alan@linux.intel.com \
--cc=arnd@arndb.de \
--cc=fweisbec@gmail.com \
--cc=jblunck@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew@wil.cx \
--cc=mingo@elte.hu \
--cc=oleg@redhat.com \
--cc=tglx@linutronix.de \
/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
Powered by JetHome