From: "Simon Sandström" <simon@nikanor.nu>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: gregkh@linuxfoundation.org, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/4] staging: kpc2000: add missing spaces in core.c
Date: Wed, 29 May 2019 17:54:19 +0200 [thread overview]
Message-ID: <20190529155419.ego3sfedew65ini5@dev.nikanor.nu> (raw)
In-Reply-To: <20190527073159.GX31203@kadam>
On Mon, May 27, 2019 at 10:31:59AM +0300, Dan Carpenter wrote:
> On Fri, May 24, 2019 at 01:08:01PM +0200, Simon Sandström wrote:
> > [..]
> > - ret = copy_to_user((void*)ioctl_param, (void*)&temp, sizeof(temp));
> > + ret = copy_to_user((void *)ioctl_param, (void *)&temp, sizeof(temp));
> > if (ret)
> > return -EFAULT;
>
> This should really be written like so:
>
> if (copy_to_user((void __user *)ioctl_param, &temp,
> sizeof(temp)))
> return -EFAULT;
>
> temp is really the wrong name. "temp" is for temperatures. "tmp" means
> temporary. But also "tmp" is wrong here because it's not a temporary
> variable. It's better to call it "regs" here.
>
> regards,
> dan carpenter
>
I agree, but I don't think it fits within this patch. I can send a
separate patch with this change.
Thanks
- Simon
next prev parent reply other threads:[~2019-05-29 15:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-24 11:07 [PATCH 0/4] Fix whitespace issues in staging/kpc2000 Simon Sandström
2019-05-24 11:07 ` [PATCH 1/4] staging: kpc2000: add spaces around operators in core.c Simon Sandström
2019-05-30 21:05 ` Greg KH
2019-05-30 22:57 ` Matt Sickler
2019-05-31 0:11 ` Greg KH
2019-05-24 11:08 ` [PATCH 2/4] staging: kpc2000: remove extra blank line " Simon Sandström
2019-05-24 11:08 ` [PATCH 3/4] staging: kpc2000: add missing spaces " Simon Sandström
2019-05-27 7:31 ` Dan Carpenter
2019-05-29 15:54 ` Simon Sandström [this message]
2019-05-29 18:15 ` Dan Carpenter
2019-05-24 11:08 ` [PATCH 4/4] staging: kpc2000: remove extra " Simon Sandström
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=20190529155419.ego3sfedew65ini5@dev.nikanor.nu \
--to=simon@nikanor.nu \
--cc=dan.carpenter@oracle.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®