From: Dust Li <dust.li@linux.alibaba.com>
To: Nicolai Buchwitz <nb@tipi-net.de>,
Jakub Kicinski <kuba@kernel.org>,
alibuda@linux.alibaba.com, sidraya@linux.ibm.com,
mjambigi@linux.ibm.com
Cc: Chengfeng Ye <nicoyip.dev@gmail.com>,
davem@davemloft.net, edumazet@kernel.org, pabeni@redhat.com,
tonylu@linux.alibaba.com, guwen@linux.alibaba.com,
horms@kernel.org, linux-rdma@vger.kernel.org,
linux-s390@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH net v3 0/3] net/smc: fix link group scheduling, registration and work lifetime
Date: Wed, 21 Oct 2026 20:13:43 +0800 [thread overview]
Message-ID: <atisd5Nbof9AS5yq@linux.alibaba.com> (raw)
In-Reply-To: <1F2D6162-5113-41DE-B649-0E67F037E8CD@tipi-net.de>
On 2026-10-21 07:44:28, Nicolai Buchwitz wrote:
>
>
>On October 21, 2026 2:02:23 AM GMT+02:00, Dust Li <dust.li@linux.alibaba.com> wrote:
>
>> [...]
>
>>Are there any guidelines or mechanisms that can help with this?
>
>You can use suie and filter (funnel icon) for your driver(s). The filter is AFAIK populated from MAINTAINERS file.
>
>For me this helps a lot, to keep an eye on patches and their state.
>
>[1] https://netdev.bots.linux.dev/suie.html?delegate=netdev
Didn't know about this tool before. Thanks for sharing, really
helpful!
Best regards,
Dust
prev parent reply other threads:[~2026-10-21 12:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-13 9:17 [PATCH net v3 0/3] net/smc: fix link group scheduling, registration and work lifetime Chengfeng Ye
2026-10-13 9:17 ` [PATCH net v3 1/3] net/smc: serialize link group free work scheduling Chengfeng Ye
2026-10-13 9:17 ` [PATCH net v3 2/3] net/smc: serialize early link group cleanup with termination Chengfeng Ye
2026-10-14 9:19 ` netdev-bot+sashiko
2026-10-21 12:13 ` Dust Li
2026-10-13 9:17 ` [PATCH net v3 3/3] net/smc: hold a link group reference for free work Chengfeng Ye
2026-10-20 19:58 ` [PATCH net v3 0/3] net/smc: fix link group scheduling, registration and work lifetime Jakub Kicinski
2026-10-21 0:02 ` Dust Li
2026-10-21 5:44 ` Nicolai Buchwitz
2026-10-21 12:13 ` Dust Li [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=atisd5Nbof9AS5yq@linux.alibaba.com \
--to=dust.li@linux.alibaba.com \
--cc=alibuda@linux.alibaba.com \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=guwen@linux.alibaba.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=mjambigi@linux.ibm.com \
--cc=nb@tipi-net.de \
--cc=netdev@vger.kernel.org \
--cc=nicoyip.dev@gmail.com \
--cc=pabeni@redhat.com \
--cc=sidraya@linux.ibm.com \
--cc=stable@vger.kernel.org \
--cc=tonylu@linux.alibaba.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