From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Jia He <hejianet@gmail.com>
Cc: linux-kernel@vger.kernel.org, Oleg Drokin <oleg.drokin@intel.com>,
Andreas Dilger <andreas.dilger@intel.com>
Subject: Re: [PATCH] staging: lustre: Fix sparse warning on address-space
Date: Sat, 17 Jan 2015 15:53:55 -0800 [thread overview]
Message-ID: <20150117235355.GA23254@kroah.com> (raw)
In-Reply-To: <1419857380-16496-1-git-send-email-hejianet@gmail.com>
On Mon, Dec 29, 2014 at 08:49:40PM +0800, Jia He wrote:
> This patch is to fix the below warnings generated by sparse:
> warning: incorrect type in argument 1 (different address spaces)
> expected void const volatile [noderef] <asn:1>*<noident>
> got int *<noident>
> Adding the macro "__user" can suppress the warnings, and aslo some lines
> are adjusted for 80 chars line limitation.
> Already checked by sparse "C=2"
>
> Signed-off-by: Jia He <hejianet@gmail.com>
> Cc: Oleg Drokin <oleg.drokin@intel.com>
> Cc: Andreas Dilger <andreas.dilger@intel.com>
> Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> ---
> .../staging/lustre/lustre/include/lprocfs_status.h | 18 ++++-----
> .../lustre/lustre/obdclass/lprocfs_status.c | 6 +--
> drivers/staging/lustre/lustre/osc/lproc_osc.c | 44 +++++++++++-----------
> drivers/staging/lustre/lustre/osc/osc_request.c | 6 +--
> .../staging/lustre/lustre/ptlrpc/lproc_ptlrpc.c | 6 +--
> 5 files changed, 40 insertions(+), 40 deletions(-)
Doesn't apply to my staging-testing branch at all :(
prev parent reply other threads:[~2015-01-18 0:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-29 12:49 [PATCH] staging: lustre: Fix sparse warning on address-space Jia He
2015-01-14 3:50 ` hejianet
2015-01-17 23:53 ` 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=20150117235355.GA23254@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=andreas.dilger@intel.com \
--cc=hejianet@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg.drokin@intel.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.