From: Oleg Drokin <oleg.drokin@intel.com>
To: Rui Teng <rui.teng@linux.vnet.ibm.com>
Cc: Andreas Dilger <andreas.dilger@intel.com>,
James Simmons <jsimmons@infradead.org>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
<lustre-devel@lists.lustre.org>, <devel@driverdev.osuosl.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] stating: lustre: fix sparse error: incompatible types in comparison expression
Date: Thu, 13 Jul 2017 00:29:44 -0400 [thread overview]
Message-ID: <C93C23FD-C96C-4EF0-A622-AE060EB87203@intel.com> (raw)
In-Reply-To: <20170713021017.5368-1-rui.teng@linux.vnet.ibm.com>
On Jul 12, 2017, at 10:10 PM, Rui Teng wrote:
> Comparing two user space addresses to avoid sparse error:
>
> drivers/staging//lustre/lnet/selftest/conrpc.c:490:30: error:
> incompatible types in comparison expression (different address spaces)
>
> Signed-off-by: Rui Teng <rui.teng@linux.vnet.ibm.com>
> ---
> drivers/staging/lustre/lnet/selftest/conrpc.c | 5 ++---
> 1 file changed, 2 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/staging/lustre/lnet/selftest/conrpc.c b/drivers/staging/lustre/lnet/selftest/conrpc.c
> index da36c55b86d3..ae7c2772825e 100644
> --- a/drivers/staging/lustre/lnet/selftest/conrpc.c
> +++ b/drivers/staging/lustre/lnet/selftest/conrpc.c
> @@ -487,10 +487,9 @@ lstcon_rpc_trans_interpreter(struct lstcon_rpc_trans *trans,
> sizeof(struct list_head)))
> return -EFAULT;
>
> - if (tmp.next == head_up)
> - return 0;
> -
> next = tmp.next;
So the assignment is fine, but comparison is not? Strange.
I guess this is fine by me if that makes the warning go away.
Acked-by: Oleg Drokin <oleg.drokin@intel.com>
> + if (next == head_up)
> + return 0;
>
> ent = list_entry(next, struct lstcon_rpc_ent, rpe_link);
>
> --
> 2.11.0
prev parent reply other threads:[~2017-07-13 4:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-13 2:10 Rui Teng
2017-07-13 4:29 ` Oleg Drokin [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=C93C23FD-C96C-4EF0-A622-AE060EB87203@intel.com \
--to=oleg.drokin@intel.com \
--cc=andreas.dilger@intel.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=jsimmons@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lustre-devel@lists.lustre.org \
--cc=rui.teng@linux.vnet.ibm.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 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®