From: patchwork-bot+netdevbpf@kernel.org
To: Nathan Huckleberry <nhuck@google.com>
Cc: error27@gmail.com, llvm@lists.linux.dev, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
kgugala@antmicro.com, mholenko@antmicro.com, gsomlo@gmail.com,
joel@jms.id.au, nathan@kernel.org, ndesaulniers@google.com,
trix@redhat.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] net: ethernet: litex: Fix return type of liteeth_start_xmit
Date: Tue, 20 Sep 2022 01:40:17 +0000 [thread overview]
Message-ID: <166363801725.6857.8934442480549905772.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220912195307.812229-1-nhuck@google.com>
Hello:
This patch was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 12 Sep 2022 12:53:07 -0700 you wrote:
> The ndo_start_xmit field in net_device_ops is expected to be of type
> netdev_tx_t (*ndo_start_xmit)(struct sk_buff *skb, struct net_device *dev).
>
> The mismatched return type breaks forward edge kCFI since the underlying
> function definition does not match the function hook definition.
>
> The return type of liteeth_start_xmit should be changed from int to
> netdev_tx_t.
>
> [...]
Here is the summary with links:
- net: ethernet: litex: Fix return type of liteeth_start_xmit
https://git.kernel.org/netdev/net-next/c/40662333dd7c
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-09-20 1:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-12 19:53 [PATCH] net: ethernet: litex: Fix return type of liteeth_start_xmit Nathan Huckleberry
2022-09-13 22:31 ` Nathan Chancellor
2022-09-14 12:06 ` Gabriel L. Somlo
2022-09-20 1:40 ` 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=166363801725.6857.8934442480549905772.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=error27@gmail.com \
--cc=gsomlo@gmail.com \
--cc=joel@jms.id.au \
--cc=kgugala@antmicro.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=mholenko@antmicro.com \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=netdev@vger.kernel.org \
--cc=nhuck@google.com \
--cc=pabeni@redhat.com \
--cc=trix@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;
as well as URLs for NNTP newsgroup(s).