From: patchwork-bot+netdevbpf@kernel.org
To: Simon Horman <simon.horman@corigine.com>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
netdev@vger.kernel.org, oss-drivers@corigine.com
Subject: Re: [PATCH net-next] Revert "nfp: update nfp_X logging definitions"
Date: Sun, 19 Jun 2022 10:30:12 +0000 [thread overview]
Message-ID: <165563461296.4100.11017570160841679295.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220619081530.228400-1-simon.horman@corigine.com>
Hello:
This patch was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:
On Sun, 19 Jun 2022 10:15:30 +0200 you wrote:
> This reverts commit 9386ebccfc59 ("nfp: update nfp_X logging definitions")
>
> The reverted patch was intended to improve logging for the NFP driver by
> including information such as the source code file and number in log
> messages.
>
> Unfortunately our experience is that this has not improved things as
> we had hoped. The resulting logs are inconsistent with (most) other
> kernel log messages. And rely on knowledge of the source code version
> in order for the extra information to be useful.
>
> [...]
Here is the summary with links:
- [net-next] Revert "nfp: update nfp_X logging definitions"
https://git.kernel.org/netdev/net-next/c/41a36d4e5a14
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:[~2022-06-19 10:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-19 8:15 [PATCH net-next] Revert "nfp: update nfp_X logging definitions" Simon Horman
2022-06-19 10: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=165563461296.4100.11017570160841679295.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=oss-drivers@corigine.com \
--cc=pabeni@redhat.com \
--cc=simon.horman@corigine.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).