From: patchwork-bot+netdevbpf@kernel.org
To: Randy Dunlap <rdunlap@infradead.org>
Cc: netdev@vger.kernel.org, lkp@intel.com, lipeng321@huawei.com,
huangguangbin2@huawei.com, yisen.zhuang@huawei.com,
salil.mehta@huawei.com, davem@davemloft.net, kuba@kernel.org
Subject: Re: [PATCH -net] net: hisilicon: fix hsn3_ethtool kernel-doc warnings
Date: Sun, 07 Nov 2021 19:30:07 +0000 [thread overview]
Message-ID: <163631340726.13867.614351698615394170.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20211106031441.3004-1-rdunlap@infradead.org>
Hello:
This patch was applied to netdev/net.git (master)
by David S. Miller <davem@davemloft.net>:
On Fri, 5 Nov 2021 20:14:41 -0700 you wrote:
> Fix kernel-doc warnings and spacing in hns3_ethtool.c:
>
> hns3_ethtool.c:246: warning: No description found for return value of 'hns3_lp_run_test'
> hns3_ethtool.c:408: warning: expecting prototype for hns3_nic_self_test(). Prototype was for hns3_self_test() instead
>
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
> Reported-by: kernel test robot <lkp@intel.com>
> Cc: Peng Li <lipeng321@huawei.com>
> Cc: Guangbin Huang <huangguangbin2@huawei.com>
> Cc: Yisen Zhuang <yisen.zhuang@huawei.com>
> Cc: Salil Mehta <salil.mehta@huawei.com>
> Cc: "David S. Miller" <davem@davemloft.net>
> Cc: Jakub Kicinski <kuba@kernel.org>
>
> [...]
Here is the summary with links:
- [-net] net: hisilicon: fix hsn3_ethtool kernel-doc warnings
https://git.kernel.org/netdev/net/c/85879f131d78
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:[~2021-11-07 19:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-06 3:14 [PATCH -net] net: hisilicon: fix hsn3_ethtool kernel-doc warnings Randy Dunlap
2021-11-07 19: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=163631340726.13867.614351698615394170.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=huangguangbin2@huawei.com \
--cc=kuba@kernel.org \
--cc=lipeng321@huawei.com \
--cc=lkp@intel.com \
--cc=netdev@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=salil.mehta@huawei.com \
--cc=yisen.zhuang@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.