From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: B K Karthik <bkkarthik@pesu.pes.edu>
Cc: devel@driverdev.osuosl.org, Xiyu Yang <xiyuyang19@fudan.edu.cn>,
linux-kernel@vger.kernel.org, Ian Abbott <abbotti@mev.co.uk>,
Al Viro <viro@zeniv.linux.org.uk>,
Michel Lespinasse <walken@google.com>,
Divyansh Kamboj <kambojdivyansh2000@gmail.com>,
Vlastimil Babka <vbabka@suse.cz>
Subject: Re: [PATCH v3] staging: comedi: comedi_fops.c: added casts to get rid of sparse warnings
Date: Thu, 16 Jul 2020 16:39:49 +0200 [thread overview]
Message-ID: <20200716143949.GA2230084@kroah.com> (raw)
In-Reply-To: <CAAhDqq3EeWGOJHaW37iQN5UgmvTf3AP10fhrVdJ5GuYjBt8f3w@mail.gmail.com>
On Thu, Jul 16, 2020 at 10:28:06AM -0400, B K Karthik wrote:
> On Thu, Jul 16, 2020 at 10:25 AM Greg Kroah-Hartman
> <gregkh@linuxfoundation.org> wrote:
> >
> > On Thu, Jul 16, 2020 at 10:17:47AM -0400, B K Karthik wrote:
> > > fixed sparse warnings by adding a cast in assignment from
> > > void [noderef] __user * to unsigned int __force *
> > > and a reverse cast in argument from
> > > unsigned int * to unsigned int __user * .
> > >
> > > Signed-off-by: B K Karthik <karthik.bk2000@live.com>
> > > ---
> > > drivers/staging/comedi/comedi_fops.c | 4 ++--
> > > 1 file changed, 2 insertions(+), 2 deletions(-)
> >
> > What changed from previous versions?
>
> As Ian Abbott said "Minor quibble: the reverse cast is actually from
> unsigned int * to"
>
> Hence this is a change in the commit description.
How was anyone supposed to know this? :)
> > That always goes below the --- line.
>
> I did not understand this sir, can you please clarify?
Please read the documentation for how to properly version patches, it's
in the submitting patches document. Do that and send a v4 for this.
thanks,
greg k-h
prev parent reply other threads:[~2020-07-16 14:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-16 14:17 [PATCH v3] staging: comedi: comedi_fops.c: added casts to get rid of sparse warnings B K Karthik
2020-07-16 14:25 ` Greg Kroah-Hartman
2020-07-16 14:28 ` B K Karthik
2020-07-16 14:39 ` Greg Kroah-Hartman [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=20200716143949.GA2230084@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=abbotti@mev.co.uk \
--cc=bkkarthik@pesu.pes.edu \
--cc=devel@driverdev.osuosl.org \
--cc=kambojdivyansh2000@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=vbabka@suse.cz \
--cc=viro@zeniv.linux.org.uk \
--cc=walken@google.com \
--cc=xiyuyang19@fudan.edu.cn \
/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.