From: Takashi Sakamoto <o-takashi@sakamocchi.jp>
To: Arnd Bergmann <arnd@kernel.org>
Cc: Stefan Richter <stefanr@s5r6.in-berlin.de>,
linux1394-devel@lists.sourceforge.net,
"Gustavo A. R. Silva" <gustavoars@kernel.org>,
Arnd Bergmann <arnd@arndb.de>,
linux-kernel@vger.kernel.org, oscar.carter@gmail.com
Subject: Re: [PATCH] firewire: fix function type cast warning
Date: Tue, 27 Oct 2020 09:13:16 +0900 [thread overview]
Message-ID: <20201027001316.GA27589@workstation> (raw)
In-Reply-To: <20201026215138.3893732-1-arnd@kernel.org>
Hi Arnd,
On Mon, Oct 26, 2020 at 10:51:27PM +0100, Arnd Bergmann wrote:
> From: Arnd Bergmann <arnd@arndb.de>
>
> gcc -Wextra complains about a suspicious cast:
>
> rivers/firewire/core-cdev.c:985:8: warning: cast between incompatible function types from ‘void (*)(struct fw_iso_context *, dma_addr_t, void *)’ {aka ‘void (*)(struct fw_iso_context *, long long unsigned int, void *)’} to ‘void (*)(struct fw_iso_context *, u32, size_t, void *, void *)’ {aka ‘void (*)(struct fw_iso_context *, unsigned int, long unsigned int, void *, void *)’} [-Wcast-function-type]
>
> The behavior is correct in the end, but this is more clearly
> expressed using a transparent union.
>
> Fixes: 872e330e3880 ("firewire: add isochronous multichannel reception")
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
> ---
> drivers/firewire/core-cdev.c | 6 +++---
> drivers/firewire/core-iso.c | 2 +-
> include/linux/firewire.h | 17 ++++++++---------
> 3 files changed, 12 insertions(+), 13 deletions(-)
Oscar Carter has posted a patch to fix it.
https://sourceforge.net/p/linux1394/mailman/message/37024966/
I don't know exactly but maintainers seems to overlook it...
Thanks
Takashi Sakamoto
next prev parent reply other threads:[~2020-10-27 0:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-26 21:51 [PATCH] firewire: fix function type cast warning Arnd Bergmann
2020-10-27 0:13 ` Takashi Sakamoto [this message]
2020-10-27 12:48 ` Arnd Bergmann
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=20201027001316.GA27589@workstation \
--to=o-takashi@sakamocchi.jp \
--cc=arnd@arndb.de \
--cc=arnd@kernel.org \
--cc=gustavoars@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux1394-devel@lists.sourceforge.net \
--cc=oscar.carter@gmail.com \
--cc=stefanr@s5r6.in-berlin.de \
/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.