All the mail mirrored from lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Ashish Kalra <eashishkalra@gmail.com>
Cc: Joe Perches <joe@perches.com>,
	Abheek Dhawan <adawesomeguy222@gmail.com>,
	Johannes Weiner <hannes@cmpxchg.org>,
	Romain Perier <romain.perier@gmail.com>,
	Waiman Long <longman@redhat.com>,
	Allen Pais <apais@linux.microsoft.com>,
	Ivan Safonov <insafonov@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) warningJoe Perches <joe@perches.com>,
Date: Tue, 27 Apr 2021 18:09:53 +0200	[thread overview]
Message-ID: <YIg3UcWgwElAsUnI@kroah.com> (raw)
In-Reply-To: <20210427144556.GA19024@ashish>

On Tue, Apr 27, 2021 at 02:45:56PM +0000, Ashish Kalra wrote:
> Abheek Dhawan <adawesomeguy222@gmail.com>,
> Johannes Weiner <hannes@cmpxchg.org>,
> Romain Perier <romain.perier@gmail.com>,
> Waiman Long <longman@redhat.com>,
> Allen Pais <apais@linux.microsoft.com>,
> Ivan Safonov <insafonov@gmail.com>,
> linux-staging@lists.linux.dev,
> linux-kernel@vger.kernel.org

Why is this here in the email body?

> Upon running sparse, "warning: incorrect type in argument 1 (different
> address spaces) is brought to notice for this file.let's correct data type for
> variable data adding __user to make it cleaner and silence the Sparse
> warning. This is version 2 of the patch, version 1 can be found at
> https://lkml.org/lkml/2021/4/20/203

Always use lore.kernel.org links, not a random other site that we have
no idea who runs it.

And no need to say this in that form, please list below the --- line
what changed from v1.

thanks,

greg k-h

      reply	other threads:[~2021-04-27 16:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-27 14:45 [PATCH v2] staging: wlan-ng: silence incorrect type in argument 1 (different address spaces) warningJoe Perches <joe@perches.com>, Ashish Kalra
2021-04-27 16:09 ` 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=YIg3UcWgwElAsUnI@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=adawesomeguy222@gmail.com \
    --cc=apais@linux.microsoft.com \
    --cc=eashishkalra@gmail.com \
    --cc=hannes@cmpxchg.org \
    --cc=insafonov@gmail.com \
    --cc=joe@perches.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    --cc=longman@redhat.com \
    --cc=romain.perier@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 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.