From: patchwork-bot+netdevbpf@kernel.org
To: Jakub Boehm via B4 Relay <devnull+boehm.jakub.gmail.com@kernel.org>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, nathan@kernel.org, ndesaulniers@google.com,
morbo@google.com, justinstitt@google.com, gustavoars@kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
llvm@lists.linux.dev, boehm.jakub@gmail.com
Subject: Re: [PATCH] net: plip: fix break; causing plip to never transmit
Date: Sun, 20 Oct 2024 14:50:39 +0000 [thread overview]
Message-ID: <172943583925.3593495.5521515496449183220.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241015-net-plip-tx-fix-v1-1-32d8be1c7e0b@gmail.com>
Hello:
This patch was applied to netdev/net.git (main)
by Andrew Lunn <andrew@lunn.ch>:
On Tue, 15 Oct 2024 17:16:04 +0200 you wrote:
> From: Jakub Boehm <boehm.jakub@gmail.com>
>
> Since commit
> 71ae2cb30531 ("net: plip: Fix fall-through warnings for Clang")
>
> plip was not able to send any packets, this patch replaces one
> unintended break; with fallthrough; which was originally missed by
> commit 9525d69a3667 ("net: plip: mark expected switch fall-throughs").
>
> [...]
Here is the summary with links:
- net: plip: fix break; causing plip to never transmit
https://git.kernel.org/netdev/net/c/f99cf996ba5a
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:[~2024-10-20 14:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-15 15:16 [PATCH] net: plip: fix break; causing plip to never transmit Jakub Boehm via B4 Relay
2024-10-16 14:17 ` Simon Horman
2024-10-20 14: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=172943583925.3593495.5521515496449183220.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=boehm.jakub@gmail.com \
--cc=davem@davemloft.net \
--cc=devnull+boehm.jakub.gmail.com@kernel.org \
--cc=edumazet@google.com \
--cc=gustavoars@kernel.org \
--cc=justinstitt@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=morbo@google.com \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--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