From: Geliang Tang <geliangtang@163.com>
To: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
Cc: Geliang Tang <geliangtang@163.com>,
abbotti@mev.co.uk, hsweeten@visionengravers.com,
gregkh@linuxfoundation.org, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: comedi: fix sparse warning in comedi_compat32.c
Date: Sat, 20 Jun 2015 22:38:58 +0800 [thread overview]
Message-ID: <cover.1434808718.git.geliangtang@163.com> (raw)
In-Reply-To: <20150620103819.GA29626@sudip-PC>
On Sat, Jun 20, 2015 at 04:08:19PM +0530, Sudip Mukherjee wrote:
> compat_ptr is already a typecast.
> static inline void __user *compat_ptr(compat_uptr_t uptr)
> {
> return (void __user *)(unsigned long)uptr;
> }
>
> so you are adding another typecast to an already exitsing typecast. :(
>
> and besides, this also introduces one new checkpatch warning of
> line more than 80 char.
>
> regards
> sudip
Thank you for your review. I revised the patch as you suggested. Here it is.
Geliang Tang (1):
staging: comedi: fix cast warning in comedi_compat32.c
drivers/staging/comedi/comedi_compat32.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--
2.3.4
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2015-06-20 14:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-20 16:49 [PATCH] staging: comedi: fix sparse warning in comedi_compat32.c Geliang Tang
2015-06-20 10:38 ` Sudip Mukherjee
2015-06-20 14:38 ` Geliang Tang [this message]
2015-06-20 14:38 ` [PATCH v2] staging: comedi: fix cast " Geliang Tang
2015-06-22 9:43 ` Ian Abbott
2015-06-22 15:33 ` Geliang Tang
2015-06-22 15:33 ` [PATCH v3] " Geliang Tang
2015-06-22 16:08 ` Ian Abbott
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=cover.1434808718.git.geliangtang@163.com \
--to=geliangtang@163.com \
--cc=abbotti@mev.co.uk \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=hsweeten@visionengravers.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sudipm.mukherjee@gmail.com \
/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