From: "Steve Wise" <swise-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org>
To: 'Leon Romanovsky' <leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
'Doug Ledford' <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: RE: [PATCH rdma-next] RDMA/cxgb4: Annotate r2 and stag as __be32
Date: Wed, 25 Oct 2017 15:12:00 -0500 [thread overview]
Message-ID: <037e01d34dcd$845c1ce0$8d1456a0$@opengridcomputing.com> (raw)
In-Reply-To: <20171025201019.7367-1-leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
>
> Chelsio cxgb4 HW is big-endian, hence there is need to properly
> annotate r2 and stag fields as __be32 and not __u32 to fix the
> following sparse warnings.
>
> drivers/infiniband/hw/cxgb4/qp.c:614:16:
> warning: incorrect type in assignment (different base types)
> expected unsigned int [unsigned] [usertype] r2
> got restricted __be32 [usertype] <noident>
> drivers/infiniband/hw/cxgb4/qp.c:615:18:
> warning: incorrect type in assignment (different base types)
> expected unsigned int [unsigned] [usertype] stag
> got restricted __be32 [usertype] <noident>
>
> Cc: Steve Wise <swise-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org>
> Signed-off-by: Leon Romanovsky <leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Looks fine. Thanks Leon!
Reviewed-by: Steve Wise <swise-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org>
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2017-10-25 20:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-25 20:10 [PATCH rdma-next] RDMA/cxgb4: Annotate r2 and stag as __be32 Leon Romanovsky
[not found] ` <20171025201019.7367-1-leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2017-10-25 20:12 ` Steve Wise [this message]
2017-11-10 18:05 ` Doug Ledford
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='037e01d34dcd$845c1ce0$8d1456a0$@opengridcomputing.com' \
--to=swise-7bpotxp6k4+p2yhjcf5u+vpxobypeauw@public.gmane.org \
--cc=dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
/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