From: Ryusuke Konishi <konishi.ryusukelab.ntt.co.jp@osrg.net>
To: lihong.hi@gmail.com
Cc: konishi.ryusuke@lab.ntt.co.jp, linux-nilfs@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] nilfs2: fix a wrong type conversion in nilfs_ioctl()
Date: Wed, 31 Mar 2010 16:58:35 +0900 (JST) [thread overview]
Message-ID: <20100331.165835.212698315.ryusuke@osrg.net> (raw)
In-Reply-To: <20100331074100.GA11787@xhl>
On Wed, 31 Mar 2010 15:41:00 +0800, Li Hong <lihong.hi@gmail.com> wrote:
> (void * __user *) should be (void __user *)
>
> Signed-off-by: Li Hong <lihong.hi@gmail.com>
Applied. Thank you.
Ryusuke Konishi
> ---
> fs/nilfs2/ioctl.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/fs/nilfs2/ioctl.c b/fs/nilfs2/ioctl.c
> index 313d0a2..c446017 100644
> --- a/fs/nilfs2/ioctl.c
> +++ b/fs/nilfs2/ioctl.c
> @@ -648,7 +648,7 @@ static int nilfs_ioctl_get_info(struct inode *inode, struct file *filp,
> long nilfs_ioctl(struct file *filp, unsigned int cmd, unsigned long arg)
> {
> struct inode *inode = filp->f_dentry->d_inode;
> - void __user *argp = (void * __user *)arg;
> + void __user *argp = (void __user *)arg;
>
> switch (cmd) {
> case NILFS_IOCTL_CHANGE_CPMODE:
> --
> 1.6.3.3
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2010-03-31 7:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-31 7:41 [PATCH] nilfs2: fix a wrong type conversion in nilfs_ioctl() Li Hong
2010-03-31 7:58 ` Ryusuke Konishi [this message]
2010-04-02 10:43 ` [PATCH 2/2] nilfs2: Combine nilfs_btree_release_path() and nilfs_btree_free_path() Li Hong
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=20100331.165835.212698315.ryusuke@osrg.net \
--to=konishi.ryusukelab.ntt.co.jp@osrg.net \
--cc=konishi.ryusuke@lab.ntt.co.jp \
--cc=lihong.hi@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nilfs@vger.kernel.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