From: patchwork-bot+netdevbpf@kernel.org
To: Nathan Chancellor <nathan@kernel.org>
Cc: kys@microsoft.com, haiyangz@microsoft.com,
sthemmin@microsoft.com, wei.liu@kernel.org, decui@microsoft.com,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, linux-hyperv@vger.kernel.org,
netdev@vger.kernel.org, ndesaulniers@google.com, trix@redhat.com,
keescook@chromium.org, samitolvanen@google.com,
llvm@lists.linux.dev, linux-kernel@vger.kernel.org,
patches@lists.linux.dev, nhuck@google.com, error27@gmail.com
Subject: Re: [PATCH v3] net: mana: Fix return type of mana_start_xmit()
Date: Thu, 10 Nov 2022 11:40:15 +0000 [thread overview]
Message-ID: <166808041522.12004.5463540474559850111.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221109002629.1446680-1-nathan@kernel.org>
Hello:
This patch was applied to netdev/net-next.git (master)
by Paolo Abeni <pabeni@redhat.com>:
On Tue, 8 Nov 2022 17:26:30 -0700 you wrote:
> From: Nathan Huckleberry <nhuck@google.com>
>
> 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. A new
> warning in clang will catch this at compile time:
>
> [...]
Here is the summary with links:
- [v3] net: mana: Fix return type of mana_start_xmit()
https://git.kernel.org/netdev/net-next/c/0c9ef08a4d0f
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-10 11:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-09 0:26 [PATCH v3] net: mana: Fix return type of mana_start_xmit() Nathan Chancellor
2022-11-10 11: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=166808041522.12004.5463540474559850111.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=decui@microsoft.com \
--cc=edumazet@google.com \
--cc=error27@gmail.com \
--cc=haiyangz@microsoft.com \
--cc=keescook@chromium.org \
--cc=kuba@kernel.org \
--cc=kys@microsoft.com \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=netdev@vger.kernel.org \
--cc=nhuck@google.com \
--cc=pabeni@redhat.com \
--cc=patches@lists.linux.dev \
--cc=samitolvanen@google.com \
--cc=sthemmin@microsoft.com \
--cc=trix@redhat.com \
--cc=wei.liu@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 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.