From: patchwork-bot+netdevbpf@kernel•org
To: Nathan Huckleberry <nhuck@google•com>
Cc: kuba@kernel•org, Steen.Hegelund@microchip•com,
UNGLinuxDriver@microchip•com, casper.casan@gmail•com,
davem@davemloft•net, edumazet@google•com, error27@gmail•com,
horatiu.vultur@microchip•com, lars.povlsen@microchip•com,
linux-arm-kernel@lists•infradead.org,
linux-kernel@vger•kernel.org, llvm@lists•linux.dev,
nathan@kernel•org, ndesaulniers@google•com,
netdev@vger•kernel.org, pabeni@redhat•com, trix@redhat•com
Subject: Re: [PATCH v2] net: sparx5: Fix return type of sparx5_port_xmit_impl
Date: Mon, 03 Oct 2022 09:50:14 +0000 [thread overview]
Message-ID: <166479061442.29582.11755477144424955738.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220929181947.62909-1-nhuck@google.com>
Hello:
This patch was applied to netdev/net.git (master)
by David S. Miller <davem@davemloft•net>:
On Thu, 29 Sep 2022 11:19:47 -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 sparx5_port_xmit_impl should be changed from int to
> netdev_tx_t.
>
> [...]
Here is the summary with links:
- [v2] net: sparx5: Fix return type of sparx5_port_xmit_impl
https://git.kernel.org/netdev/net/c/73ea73507359
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-10-03 9:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-12 21:44 [PATCH] net: sparx5: Fix return type of sparx5_port_xmit_impl Nathan Huckleberry
2022-09-13 8:15 ` Casper Andersson
2022-09-13 20:46 ` Nathan Huckleberry
2022-09-20 14:29 ` Jakub Kicinski
2022-09-20 14:30 ` Jakub Kicinski
2022-09-29 18:19 ` [PATCH v2] " Nathan Huckleberry
2022-10-03 9: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=166479061442.29582.11755477144424955738.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel$(echo .)org \
--cc=Steen.Hegelund@microchip$(echo .)com \
--cc=UNGLinuxDriver@microchip$(echo .)com \
--cc=casper.casan@gmail$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=edumazet@google$(echo .)com \
--cc=error27@gmail$(echo .)com \
--cc=horatiu.vultur@microchip$(echo .)com \
--cc=kuba@kernel$(echo .)org \
--cc=lars.povlsen@microchip$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=llvm@lists$(echo .)linux.dev \
--cc=nathan@kernel$(echo .)org \
--cc=ndesaulniers@google$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=nhuck@google$(echo .)com \
--cc=pabeni@redhat$(echo .)com \
--cc=trix@redhat$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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