From: Jakub Kicinski <kuba@kernel.org>
To: Fushuai Wang <fushuai.wang@linux.dev>
Cc: davem@davemloft.net, edumazet@google.com, pabeni@redhat.com,
horms@kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, wangfushuai@baidu.com
Subject: Re: [PATCH] rtnl: Add guard support
Date: Fri, 28 Nov 2025 19:45:00 -0800 [thread overview]
Message-ID: <20251128194500.052b780f@kernel.org> (raw)
In-Reply-To: <20251128083455.67474-1-fushuai.wang@linux.dev>
On Fri, 28 Nov 2025 16:34:55 +0800 Fushuai Wang wrote:
> Introduce guard support to simplify the usage of the
> lock about rtnl.
We don't accept APIs without a user.
Also in this case please read:
https://www.kernel.org/doc/html/next/process/maintainer-netdev.html#using-device-managed-and-cleanup-h-constructs
--
pw-bot: reject
next prev parent reply other threads:[~2025-11-29 3:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-28 8:34 [PATCH] rtnl: Add guard support Fushuai Wang
2025-11-29 3:45 ` Jakub Kicinski [this message]
2025-11-29 8:35 ` Eric Dumazet
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=20251128194500.052b780f@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=fushuai.wang@linux.dev \
--cc=horms@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=wangfushuai@baidu.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;
as well as URLs for NNTP newsgroup(s).