From: patchwork-bot+netdevbpf@kernel.org
To: Wan Jiabing <wanjiabing@vivo.com>
Cc: simon.horman@corigine.com, kuba@kernel.org, davem@davemloft.net,
baowen.zheng@corigine.com, louis.peens@corigine.com,
jianbol@nvidia.com, peng.zhang@corigine.com,
oss-drivers@corigine.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, kael_w@qq.com
Subject: Re: [PATCH] nfp: avoid newline at end of message in NL_SET_ERR_MSG_MOD
Date: Wed, 02 Mar 2022 02:00:10 +0000 [thread overview]
Message-ID: <164618641028.32282.3941297685068677511.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220301112356.1820985-1-wanjiabing@vivo.com>
Hello:
This patch was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 1 Mar 2022 19:23:54 +0800 you wrote:
> Fix the following coccicheck warning:
> ./drivers/net/ethernet/netronome/nfp/flower/qos_conf.c:750:7-55: WARNING
> avoid newline at end of message in NL_SET_ERR_MSG_MOD
>
> Signed-off-by: Wan Jiabing <wanjiabing@vivo.com>
> ---
> drivers/net/ethernet/netronome/nfp/flower/qos_conf.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Here is the summary with links:
- nfp: avoid newline at end of message in NL_SET_ERR_MSG_MOD
https://git.kernel.org/netdev/net-next/c/323d51cac6a1
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-03-02 2:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-01 11:23 [PATCH] nfp: avoid newline at end of message in NL_SET_ERR_MSG_MOD Wan Jiabing
2022-03-01 13:02 ` Simon Horman
2022-03-02 2:00 ` 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=164618641028.32282.3941297685068677511.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=baowen.zheng@corigine.com \
--cc=davem@davemloft.net \
--cc=jianbol@nvidia.com \
--cc=kael_w@qq.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=louis.peens@corigine.com \
--cc=netdev@vger.kernel.org \
--cc=oss-drivers@corigine.com \
--cc=peng.zhang@corigine.com \
--cc=simon.horman@corigine.com \
--cc=wanjiabing@vivo.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).