From: gyang <graf.yang@analog.com>
To: stoyboyker@gmail.com
Cc: linux-kernel@vger.kernel.org, uclinux-dist-devel@blackfin.uclinux.org
Subject: Re: [Uclinux-dist-devel] [PATCH 04/13] [blackfin] changed ioctls to unlocked
Date: Wed, 25 Mar 2009 10:07:56 +0800 [thread overview]
Message-ID: <1237946876.5927.3.camel@dy> (raw)
In-Reply-To: <1237929168-15341-5-git-send-email-stoyboyker@gmail.com>
Could you add some comment for this patch?
On Tue, 2009-03-24 at 16:12 -0500, stoyboyker@gmail.com wrote:
> From: Stoyan Gaydarov <stoyboyker@gmail.com>
>
> Signed-off-by: Stoyan Gaydarov <stoyboyker@gmail.com>
> ---
> arch/blackfin/mach-bf561/coreb.c | 8 +++++---
> 1 files changed, 5 insertions(+), 3 deletions(-)
>
> diff --git a/arch/blackfin/mach-bf561/coreb.c b/arch/blackfin/mach-bf561/coreb.c
> index 8598098..9ad89af 100644
> --- a/arch/blackfin/mach-bf561/coreb.c
> +++ b/arch/blackfin/mach-bf561/coreb.c
> @@ -220,9 +220,10 @@ static int coreb_release(struct inode *inode, struct file *file)
> return 0;
> }
>
> -static int coreb_ioctl(struct inode *inode, struct file *file,
> - unsigned int cmd, unsigned long arg)
> +static long coreb_ioctl(struct file *file, unsigned int cmd, unsigned long arg)
> {
> + lock_kernel();
> +
> int retval = 0;
> int coreb_index = 0;
>
> @@ -289,6 +290,7 @@ static int coreb_ioctl(struct inode *inode, struct file *file,
> #endif
> }
>
> + unlock_kernel();
> return retval;
> }
>
> @@ -297,7 +299,7 @@ static struct file_operations coreb_fops = {
> .llseek = coreb_lseek,
> .read = coreb_read,
> .write = coreb_write,
> - .ioctl = coreb_ioctl,
> + .unlocked_ioctl = coreb_ioctl,
> .open = coreb_open,
> .release = coreb_release
> };
next prev parent reply other threads:[~2009-03-25 2:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-24 21:12 [PATCH 04/13] [blackfin] changed ioctls to unlocked stoyboyker
2009-03-25 2:07 ` gyang [this message]
2009-03-25 2:31 ` Mike Frysinger
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=1237946876.5927.3.camel@dy \
--to=graf.yang@analog.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stoyboyker@gmail.com \
--cc=uclinux-dist-devel@blackfin.uclinux.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 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.