Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Subject: Re: [PATCH] hamradio: baycom_epp: Fix return type of baycom_send_packet()
From:   patchwork-bot+netdevbpf@kernel.org
Message-Id: <166753802702.27738.11594925007780721329.git-patchwork-notify@kernel.org>
Date:   Fri, 04 Nov 2022 05:00:27 +0000
References: <20221102160610.1186145-1-nathan@kernel.org>
In-Reply-To: <20221102160610.1186145-1-nathan@kernel.org>
To:     Nathan Chancellor <nathan@kernel.org>
Cc:     t.sailer@alumni.ethz.ch, davem@davemloft.net, edumazet@google.com,
        kuba@kernel.org, pabeni@redhat.com, linux-hams@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
Precedence: bulk

Hello:

This patch was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel.org>:

On Wed,  2 Nov 2022 09:06:10 -0700 you wrote:
> With clang's kernel control flow integrity (kCFI, CONFIG_CFI_CLANG),
> indirect call targets are validated against the expected function
> pointer prototype to make sure the call target is valid to help mitigate
> ROP attacks. If they are not identical, there is a failure at run time,
> which manifests as either a kernel panic or thread getting killed. A
> proposed warning in clang aims to catch these at compile time, which
> reveals:
> 
> [...]

Here is the summary with links:
  - hamradio: baycom_epp: Fix return type of baycom_send_packet()
    https://git.kernel.org/netdev/net-next/c/c5733e5b15d9

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html