From: patchwork-bot+netdevbpf@kernel.org
To: Jiri Slaby <jirislaby@kernel.org>
Cc: ecree.xilinx@gmail.com, linux-kernel@vger.kernel.org,
mliska@suse.cz, habetsm.xilinx@gmail.com, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
netdev@vger.kernel.org
Subject: Re: [PATCH] sfc (gcc13): synchronize ef100_enqueue_skb()'s return type
Date: Thu, 03 Nov 2022 03:50:18 +0000 [thread overview]
Message-ID: <166744741893.12191.4306844598535321397.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221031114440.10461-1-jirislaby@kernel.org>
Hello:
This patch was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 31 Oct 2022 12:44:40 +0100 you wrote:
> ef100_enqueue_skb() generates a valid warning with gcc-13:
> drivers/net/ethernet/sfc/ef100_tx.c:370:5: error: conflicting types for 'ef100_enqueue_skb' due to enum/integer mismatch; have 'int(struct efx_tx_queue *, struct sk_buff *)'
> drivers/net/ethernet/sfc/ef100_tx.h:25:13: note: previous declaration of 'ef100_enqueue_skb' with type 'netdev_tx_t(struct efx_tx_queue *, struct sk_buff *)'
>
> I.e. the type of the ef100_enqueue_skb()'s return value in the declaration is
> int, while the definition spells enum netdev_tx_t. Synchronize them to the
> latter.
>
> [...]
Here is the summary with links:
- sfc (gcc13): synchronize ef100_enqueue_skb()'s return type
https://git.kernel.org/netdev/net-next/c/3319dbb3e755
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2022-11-03 3:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-31 11:44 [PATCH] sfc (gcc13): synchronize ef100_enqueue_skb()'s return type Jiri Slaby (SUSE)
2022-11-03 3:50 ` patchwork-bot+netdevbpf [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=166744741893.12191.4306844598535321397.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=ecree.xilinx@gmail.com \
--cc=edumazet@google.com \
--cc=habetsm.xilinx@gmail.com \
--cc=jirislaby@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mliska@suse.cz \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox