From: Nikolay Aleksandrov <razor@blackwall.org>
To: Marco Crivellari <marco.crivellari@suse.com>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
bridge@lists.linux.dev
Cc: Tejun Heo <tj@kernel.org>, Lai Jiangshan <jiangshanlai@gmail.com>,
Frederic Weisbecker <frederic@kernel.org>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Michal Hocko <mhocko@suse.com>, Simon Horman <horms@verge.net.au>,
"David S . Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Ido Schimmel <idosch@nvidia.com>
Subject: Re: [RFC PATCH net-next] net: bridge: Move long delayed work on system_dfl_long_wq
Date: Fri, 5 Jun 2026 11:21:07 +0300 [thread overview]
Message-ID: <8186bef1-aa58-47c5-9816-1b707ec949da@blackwall.org> (raw)
In-Reply-To: <4d9067d9-2a4a-45e2-aa43-c456648989da@blackwall.org>
On 05/06/2026 11:20, Nikolay Aleksandrov wrote:
> On 05/06/2026 11:16, Marco Crivellari wrote:
>> Hi,
>>
>> On Thu, May 7, 2026 at 3:48 PM Marco Crivellari
>> <marco.crivellari@suse.com> wrote:
>>> [...]
>>> net/bridge/br_fdb.c | 2 +-
>>> net/bridge/br_stp.c | 2 +-
>>> net/bridge/br_stp_if.c | 2 +-
>>> 3 files changed, 3 insertions(+), 3 deletions(-)
>>
>> Gentle ping.
>>
>> Thanks!
>>
>
> Ping about what? The patch is marked as RFC so it is not
> going to be considered. It already got a reviewed-by one
err, considered to be applied
> of the maintainers, I'm ok with it too, so when sending it please add:
>
> Acked-by: Nikolay Aleksandrov <razor@blackwall.org>
>
> Cheers,
> Nik
next prev parent reply other threads:[~2026-06-05 8:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-07 13:48 [RFC PATCH net-next] net: bridge: Move long delayed work on system_dfl_long_wq Marco Crivellari
2026-05-10 15:54 ` Ido Schimmel
2026-06-05 8:16 ` Marco Crivellari
2026-06-05 8:20 ` Nikolay Aleksandrov
2026-06-05 8:21 ` Nikolay Aleksandrov [this message]
2026-06-05 8:24 ` Marco Crivellari
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=8186bef1-aa58-47c5-9816-1b707ec949da@blackwall.org \
--to=razor@blackwall.org \
--cc=bigeasy@linutronix.de \
--cc=bridge@lists.linux.dev \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=frederic@kernel.org \
--cc=horms@verge.net.au \
--cc=idosch@nvidia.com \
--cc=jiangshanlai@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marco.crivellari@suse.com \
--cc=mhocko@suse.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=tj@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox