From: ashish <eashishkalra@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Ashish Kalra <eashishkalra@gmail.com>,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] staging: wlan-ng: silence incorrect type in argument 1 (different address spaces)
Date: Tue, 27 Apr 2021 18:04:36 +0000 [thread overview]
Message-ID: <20210427180436.GA37280@ashish> (raw)
In-Reply-To: <YIj6dw5afJ1bBYWK@kroah.com>
On Wed, Apr 28, 2021 at 08:02:31AM +0200, Greg Kroah-Hartman wrote:
> On Tue, Apr 27, 2021 at 04:58:44PM +0000, Ashish Kalra wrote:
> > Corrected data type for variable data adding __user to make it cleaner and silence the Sparse warning. This is version 2 of patch, version 1 can be found at https://lore.kernel.org/linux-staging/20210420090142.GA4086@ashish-NUC8i5BEH/
> >
> > Signed-off-by: Ashish Kalra <eashishkalra@gmail.com>
> > ---
> >
> > Changes from v1: removed type casting of (void __user *) for req->data and corrected type for data to include __user
>
> Did you send this twice?
>
> And please wrap your changelog text and put proper information in it,
> not references to previous patches.
>
> thanks,
>
> greg k-h
Thanks Greg
Sorry for sending twice due to some issue in To list
I have corrected and send again as per your inputs
hopefully it will be ok now
next prev parent reply other threads:[~2021-04-28 6:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-27 16:58 [PATCH v2] staging: wlan-ng: silence incorrect type in argument 1 (different address spaces) Ashish Kalra
2021-04-28 6:02 ` Greg Kroah-Hartman
2021-04-27 18:04 ` ashish [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-04-27 17:22 Ashish Kalra
2021-04-27 18:03 Ashish Kalra
2021-05-01 11:39 Ashish Kalra
2021-05-01 12:23 ` Greg Kroah-Hartman
2021-05-01 13:54 ` Ashish
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=20210427180436.GA37280@ashish \
--to=eashishkalra@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
/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.