From: Florian Fainelli <florian.fainelli@broadcom.com>
To: stable@vger.kernel.org
Cc: "David S. Miller" <davem@davemloft.net>,
"Pravin B Shelar" <pshelar@ovn.org>,
"Alexei Starovoitov" <ast@kernel.org>,
"Daniel Borkmann" <daniel@iogearbox.net>,
"Martin KaFai Lau" <kafai@fb.com>,
"Song Liu" <songliubraving@fb.com>, "Yonghong Song" <yhs@fb.com>,
"Andrii Nakryiko" <andriin@fb.com>,
"Sasha Levin" <sashal@kernel.org>,
"Eric Dumazet" <edumazet@google.com>,
"Willem de Bruijn" <willemb@google.com>,
"Jakub Kicinski" <kuba@kernel.org>,
"David Ahern" <dsahern@kernel.org>,
"Benoît Monin" <benoit.monin@gmx.fr>,
"Xin Long" <lucien.xin@gmail.com>,
"Felix Huettner" <felix.huettner@mail.schwarz>,
"open list:NETWORKING [GENERAL]" <netdev@vger.kernel.org>,
"open list" <linux-kernel@vger.kernel.org>,
"open list:OPENVSWITCH" <dev@openvswitch.org>,
"open list:BPF (Safe dynamic programs and tools)"
<bpf@vger.kernel.org>
Subject: Re: [PATCH stable 5.4 0/2] openvswitch port output fixes
Date: Mon, 17 Mar 2025 09:49:00 -0700 [thread overview]
Message-ID: <2464508f-864e-4697-8fd5-ffa5c06f64a0@broadcom.com> (raw)
In-Reply-To: <20250317154023.3470515-1-florian.fainelli@broadcom.com>
On 3/17/25 08:40, Florian Fainelli wrote:
> This patch series contains some missing openvswitch port output fixes
> for the stable 5.4 kernel.
Scratch that and the two others targeting 5.10 and 5.15, I missed that
DEBUG_NET_WARN_ON_ONCE was not added until later. Will submit a v2 later
today. Thanks!
--
Florian
prev parent reply other threads:[~2025-03-17 16:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-17 15:40 [PATCH stable 5.4 0/2] openvswitch port output fixes Florian Fainelli
2025-03-17 15:40 ` [PATCH stable 5.4 1/2] net: openvswitch: fix race on port output Florian Fainelli
2025-03-17 15:40 ` [PATCH stable 5.4 2/2] openvswitch: fix lockup on tx to unregistering netdev with carrier Florian Fainelli
2025-03-17 16:49 ` Florian Fainelli [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=2464508f-864e-4697-8fd5-ffa5c06f64a0@broadcom.com \
--to=florian.fainelli@broadcom.com \
--cc=andriin@fb.com \
--cc=ast@kernel.org \
--cc=benoit.monin@gmx.fr \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=dev@openvswitch.org \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=felix.huettner@mail.schwarz \
--cc=kafai@fb.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lucien.xin@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pshelar@ovn.org \
--cc=sashal@kernel.org \
--cc=songliubraving@fb.com \
--cc=stable@vger.kernel.org \
--cc=willemb@google.com \
--cc=yhs@fb.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