From: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] usb: yurex: fixed sparse warning of incorrect type
Date: Mon, 3 Nov 2014 15:19:51 +0530 [thread overview]
Message-ID: <20141103094951.GA3153@sudip-PC> (raw)
In-Reply-To: <1412945386-4781-1-git-send-email-sudipm.mukherjee@gmail.com>
On Fri, Oct 10, 2014 at 06:19:45PM +0530, Sudip Mukherjee wrote:
> fixed sparse warning of
> 1) incorrect type (different address spaces)
> 2) incorrect type in initializer
>
> Signed-off-by: Sudip Mukherjee <sudip@vectorindia.org>
> ---
> drivers/usb/misc/yurex.c | 6 ++++--
> 1 file changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/usb/misc/yurex.c b/drivers/usb/misc/yurex.c
> index c3a45da..343fa6f 100644
> --- a/drivers/usb/misc/yurex.c
> +++ b/drivers/usb/misc/yurex.c
> @@ -410,7 +410,8 @@ static int yurex_release(struct inode *inode, struct file *file)
> return 0;
> }
>
> -static ssize_t yurex_read(struct file *file, char *buffer, size_t count, loff_t *ppos)
> +static ssize_t yurex_read(struct file *file, char __user *buffer, size_t count,
> + loff_t *ppos)
> {
> struct usb_yurex *dev;
> int retval = 0;
> @@ -444,7 +445,8 @@ exit:
> return retval;
> }
>
> -static ssize_t yurex_write(struct file *file, const char *user_buffer, size_t count, loff_t *ppos)
> +static ssize_t yurex_write(struct file *file, const char __user *user_buffer,
> + size_t count, loff_t *ppos)
> {
> struct usb_yurex *dev;
> int i, set = 0, retval = 0;
> --
> 1.8.1.2
>
gentle ping
thanks
sudip
prev parent reply other threads:[~2014-11-03 9:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-10 12:49 [PATCH] usb: yurex: fixed sparse warning of incorrect type Sudip Mukherjee
2014-11-03 9:49 ` Sudip Mukherjee [this message]
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=20141103094951.GA3153@sudip-PC \
--to=sudipm.mukherjee@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@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