From: Jason Gunthorpe <jgg@nvidia.com>
To: Alok Prasad <palok@marvell.com>
Cc: <dledford@redhat.com>, <linux-rdma@vger.kernel.org>,
Igor Russkikh <irusskikh@marvell.com>,
Michal Kalderon <mkalderon@marvell.com>
Subject: Re: [PATCH rdma-next] RDMA/qedr: endianness warnings cleanup
Date: Thu, 1 Oct 2020 20:50:55 -0300 [thread overview]
Message-ID: <20201001235055.GA1209456@nvidia.com> (raw)
In-Reply-To: <20201001100959.19940-1-palok@marvell.com>
On Thu, Oct 01, 2020 at 10:09:59AM +0000, Alok Prasad wrote:
> Making a change to fix following sparse warnings
> reported by kbuild bot.
>
> CHECK drivers/infiniband/hw/qedr/verbs.c
>
> drivers/infiniband/hw/qedr/verbs.c:3872:59: warning: incorrect type in assignment (different base types)
> drivers/infiniband/hw/qedr/verbs.c:3872:59: expected restricted __le32 [usertype] sge_prod
> drivers/infiniband/hw/qedr/verbs.c:3872:59: got unsigned int [usertype] sge_prod
> drivers/infiniband/hw/qedr/verbs.c:3875:59: warning: incorrect type in assignment (different base types)
> drivers/infiniband/hw/qedr/verbs.c:3875:59: expected restricted __le32 [usertype] wqe_prod
> drivers/infiniband/hw/qedr/verbs.c:3875:59: got unsigned int [usertype] wqe_prod
>
> Reported-by: kbuild test robot <lkp@intel.com>
> Fixes: acca72e2b031 ("RDMA/qedr: SRQ's bug fixes")
> Signed-off-by: Igor Russkikh <irusskikh@marvell.com>
> Signed-off-by: Michal Kalderon <mkalderon@marvell.com>
> Signed-off-by: Alok Prasad <palok@marvell.com>
> ---
> drivers/infiniband/hw/qedr/verbs.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
Applied to for-next
Thanks,
Jason
prev parent reply other threads:[~2020-10-01 23:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-01 10:09 [PATCH rdma-next] RDMA/qedr: endianness warnings cleanup Alok Prasad
2020-10-01 23:50 ` Jason Gunthorpe [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=20201001235055.GA1209456@nvidia.com \
--to=jgg@nvidia.com \
--cc=dledford@redhat.com \
--cc=irusskikh@marvell.com \
--cc=linux-rdma@vger.kernel.org \
--cc=mkalderon@marvell.com \
--cc=palok@marvell.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.