From: patchwork-bot+bluetooth@kernel.org
To: Wang Liang <wangliang74@huawei.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, horms@kernel.org, alex.aring@gmail.com,
dsahern@kernel.org, yuehaibing@huawei.com,
zhangchangzhong@huawei.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-bluetooth@vger.kernel.org,
linux-wpan@vger.kernel.org
Subject: Re: [PATCH net-next v3] net: replace ND_PRINTK with dynamic debug
Date: Wed, 23 Jul 2025 15:59:27 +0000 [thread overview]
Message-ID: <175328636724.1599213.15305193300784446965.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250708033342.1627636-1-wangliang74@huawei.com>
Hello:
This patch was applied to bluetooth/bluetooth-next.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 8 Jul 2025 11:33:42 +0800 you wrote:
> ND_PRINTK with val > 1 only works when the ND_DEBUG was set in compilation
> phase. Replace it with dynamic debug. Convert ND_PRINTK with val <= 1 to
> net_{err,warn}_ratelimited, and convert the rest to net_dbg_ratelimited.
>
> Suggested-by: Ido Schimmel <idosch@idosch.org>
> Signed-off-by: Wang Liang <wangliang74@huawei.com>
>
> [...]
Here is the summary with links:
- [net-next,v3] net: replace ND_PRINTK with dynamic debug
https://git.kernel.org/bluetooth/bluetooth-next/c/96698d1898bc
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:[~2025-07-23 15:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-08 3:33 [PATCH net-next v3] net: replace ND_PRINTK with dynamic debug Wang Liang
2025-07-08 4:23 ` [net-next,v3] " bluez.test.bot
2025-07-09 13:10 ` [PATCH net-next v3] " Ido Schimmel
2025-07-11 0:31 ` patchwork-bot+netdevbpf
2025-07-23 15:59 ` patchwork-bot+bluetooth [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=175328636724.1599213.15305193300784446965.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=alex.aring@gmail.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wpan@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=wangliang74@huawei.com \
--cc=yuehaibing@huawei.com \
--cc=zhangchangzhong@huawei.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.