From: Leon Romanovsky <leon@kernel.org>
To: Bart Van Assche <bvanassche@acm.org>, Arnd Bergmann <arnd@kernel.org>
Cc: Arnd Bergmann <arnd@arndb.de>, Jason Gunthorpe <jgg@ziepe.ca>,
Nathan Chancellor <nathan@kernel.org>,
Nick Desaulniers <ndesaulniers@google.com>,
Bill Wendling <morbo@google.com>,
Justin Stitt <justinstitt@google.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
"Nicholas A. Bellinger" <nab@risingtidesystems.com>,
linux-rdma@vger.kernel.org, target-devel@vger.kernel.org,
linux-kernel@vger.kernel.org, llvm@lists.linux.dev
Subject: Re: [PATCH] RDMA/srpt: fix function pointer cast warnings
Date: Wed, 14 Feb 2024 11:24:48 +0200 [thread overview]
Message-ID: <170790268857.386715.10695124519923198536.b4-ty@kernel.org> (raw)
In-Reply-To: <20240213100728.458348-1-arnd@kernel.org>
On Tue, 13 Feb 2024 11:07:13 +0100, Arnd Bergmann wrote:
> clang-16 notices that srpt_qp_event() gets called through an incompatible
> pointer here:
>
> drivers/infiniband/ulp/srpt/ib_srpt.c:1815:5: error: cast from 'void (*)(struct ib_event *, struct srpt_rdma_ch *)' to 'void (*)(struct ib_event *, void *)' converts to incompatible function type [-Werror,-Wcast-function-type-strict]
> 1815 | = (void(*)(struct ib_event *, void*))srpt_qp_event;
>
> Change srpt_qp_event() to use the correct prototype and adjust the
> argument inside of it.
>
> [...]
Applied, thanks!
[1/1] RDMA/srpt: fix function pointer cast warnings
https://git.kernel.org/rdma/rdma/c/eb5c7465c32401
Best regards,
--
Leon Romanovsky <leon@kernel.org>
prev parent reply other threads:[~2024-02-14 9:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-13 10:07 [PATCH] RDMA/srpt: fix function pointer cast warnings Arnd Bergmann
2024-02-13 21:23 ` Bart Van Assche
2024-02-14 9:21 ` Leon Romanovsky
2024-02-14 9:24 ` Leon Romanovsky [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=170790268857.386715.10695124519923198536.b4-ty@kernel.org \
--to=leon@kernel.org \
--cc=arnd@arndb.de \
--cc=arnd@kernel.org \
--cc=bvanassche@acm.org \
--cc=jgg@ziepe.ca \
--cc=justinstitt@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=martin.petersen@oracle.com \
--cc=morbo@google.com \
--cc=nab@risingtidesystems.com \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=target-devel@vger.kernel.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).