From: Jason Gunthorpe <jgg@ziepe.ca>
To: Nathan Chancellor <natechancellor@gmail.com>
Cc: Bernard Metzler <bmt@zurich.ibm.com>,
Doug Ledford <dledford@redhat.com>,
linux-rdma@vger.kernel.org, linux-kernel@vger.kernel.org,
clang-built-linux@googlegroups.com
Subject: Re: [PATCH] rdma/siw: Use proper enumerated type in map_cqe_status
Date: Wed, 10 Jul 2019 15:26:24 -0300 [thread overview]
Message-ID: <20190710182624.GG4051@ziepe.ca> (raw)
In-Reply-To: <20190710174800.34451-1-natechancellor@gmail.com>
On Wed, Jul 10, 2019 at 10:48:00AM -0700, Nathan Chancellor wrote:
> clang warns several times:
>
> drivers/infiniband/sw/siw/siw_cq.c:31:4: warning: implicit conversion
> from enumeration type 'enum siw_wc_status' to different enumeration type
> 'enum siw_opcode' [-Wenum-conversion]
> { SIW_WC_SUCCESS, IB_WC_SUCCESS },
> ~ ^~~~~~~~~~~~~~
>
> Fixes: b0fff7317bb4 ("rdma/siw: completion queue methods")
> Link: https://github.com/ClangBuiltLinux/linux/issues/596
> Signed-off-by: Nathan Chancellor <natechancellor@gmail.com>
> ---
> drivers/infiniband/sw/siw/siw_cq.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Weird that gcc doesn't warn on this by default..
Applied to for-next, thanks
Jason
next prev parent reply other threads:[~2019-07-10 18:26 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-10 17:48 [PATCH] rdma/siw: Use proper enumerated type in map_cqe_status Nathan Chancellor
2019-07-10 18:26 ` Jason Gunthorpe [this message]
2019-07-10 23:53 ` Nick Desaulniers
2019-07-11 3:02 ` Nathan Chancellor
2019-07-11 7:44 ` Bernard Metzler
2019-07-11 8:14 ` Nathan Chancellor
2019-07-11 13:39 ` Jason Gunthorpe
2019-07-11 17:16 ` Nick Desaulniers
2019-07-11 17:18 ` Jason Gunthorpe
2019-07-11 17:30 ` Nathan Chancellor
2019-08-23 14:24 ` Jason Gunthorpe
2019-08-26 15:38 ` Nathan Chancellor
2019-08-26 15:42 ` Jason Gunthorpe
2019-08-26 23:38 ` Nathan Chancellor
2019-08-27 15:08 ` Josh Poimboeuf
2019-08-27 17:00 ` Leon Romanovsky
2019-08-27 19:23 ` Josh Poimboeuf
2019-08-27 21:27 ` Nick Desaulniers
2019-08-27 22:50 ` Nick Desaulniers
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=20190710182624.GG4051@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=bmt@zurich.ibm.com \
--cc=clang-built-linux@googlegroups.com \
--cc=dledford@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=natechancellor@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.