From: patchwork-bot+netdevbpf@kernel.org
To: Breno Leitao <leitao@debian.org>
Cc: dsahern@kernel.org, weiwan@google.com, kuba@kernel.org,
davem@davemloft.net, edumazet@google.com, pabeni@redhat.com,
leit@meta.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH RESEND net-next 1/2] net/ipv6: Remove unnecessary pr_debug() logs
Date: Wed, 24 Jan 2024 01:30:31 +0000 [thread overview]
Message-ID: <170605983120.14933.12714749424058391282.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240122181955.2391676-1-leitao@debian.org>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 22 Jan 2024 10:19:54 -0800 you wrote:
> In the ipv6 system, we have some logs basically dumping the name of the
> function that is being called. This is not ideal, since ftrace give us
> "for free". Moreover, checkpatch is not happy when touching that code:
>
> WARNING: Unnecessary ftrace-like logging - prefer using ftrace
>
> Remove debug functions that only print the current function name.
>
> [...]
Here is the summary with links:
- [RESEND,net-next,1/2] net/ipv6: Remove unnecessary pr_debug() logs
https://git.kernel.org/netdev/net-next/c/a6348a7104e0
- [RESEND,net-next,2/2] net/ipv6: resolve warning in ip6_fib.c
https://git.kernel.org/netdev/net-next/c/20df28fb5bd8
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:[~2024-01-24 1:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-22 18:19 Breno Leitao
2024-01-22 18:19 ` [PATCH RESEND net-next 2/2] net/ipv6: resolve warning in ip6_fib.c Breno Leitao
2024-01-22 19:41 ` David Ahern
2024-01-24 1:30 ` patchwork-bot+netdevbpf [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=170605983120.14933.12714749424058391282.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=leit@meta.com \
--cc=leitao@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=weiwan@google.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
all inboxes | Powered by JetHome®