From: patchwork-bot+netdevbpf@kernel.org
To: Haoyue Xu <xuhaoyue1@hisilicon.com>
Cc: davem@davemloft.net, kuba@kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, michal.simek@xilinx.com,
huangdaode@huawei.com, liyangyang20@huawei.com,
huangjunxian6@hisilicon.com, linuxarm@huawei.com,
liangwenpeng@huawei.com
Subject: Re: [PATCH net-next 0/7] net: ll_temac: Cleanup for clearing static warnings
Date: Thu, 22 Sep 2022 01:40:16 +0000 [thread overview]
Message-ID: <166381081697.5452.7754102556865331552.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220917103843.526877-1-xuhaoyue1@hisilicon.com>
Hello:
This series was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Sat, 17 Sep 2022 18:38:36 +0800 you wrote:
> Most static warnings are detected by Checkpatch.pl, mainly about:
> (1) #1: About the comments.
> (2) #2: About function name in a string.
> (3) #3: About the open parenthesis.
> (4) #4: About the else branch.
> (6) #6: About trailing statements.
> (7) #5,#7: About blank lines and spaces.
>
> [...]
Here is the summary with links:
- [net-next,1/7] net: ll_temac: fix the format of block comments
https://git.kernel.org/netdev/net-next/c/75124116520b
- [net-next,2/7] net: ll_temac: Cleanup for function name in a string
https://git.kernel.org/netdev/net-next/c/653de988eb58
- [net-next,3/7] net: ll_temac: axienet: align with open parenthesis
https://git.kernel.org/netdev/net-next/c/42f5d4d0e0d9
- [net-next,4/7] net: ll_temac: delete unnecessary else branch
https://git.kernel.org/netdev/net-next/c/7dfd0dcc5e72
- [net-next,5/7] net: ll_temac: fix the missing spaces around '='
https://git.kernel.org/netdev/net-next/c/a9f1ef7034b8
- [net-next,6/7] net: ll_temac: move trailing statements to next line
https://git.kernel.org/netdev/net-next/c/a0a850976801
- [net-next,7/7] net: ll_temac: axienet: delete unnecessary blank lines and spaces
https://git.kernel.org/netdev/net-next/c/7fe85bb3af4e
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-09-22 1:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-17 10:38 [PATCH net-next 0/7] net: ll_temac: Cleanup for clearing static warnings Haoyue Xu
2022-09-17 10:38 ` [PATCH net-next 1/7] net: ll_temac: fix the format of block comments Haoyue Xu
2022-09-17 10:38 ` [PATCH net-next 2/7] net: ll_temac: Cleanup for function name in a string Haoyue Xu
2022-09-17 10:38 ` [PATCH net-next 3/7] net: ll_temac: axienet: align with open parenthesis Haoyue Xu
2022-09-17 10:38 ` [PATCH net-next 4/7] net: ll_temac: delete unnecessary else branch Haoyue Xu
2022-09-17 10:38 ` [PATCH net-next 5/7] net: ll_temac: fix the missing spaces around '=' Haoyue Xu
2022-09-17 10:38 ` [PATCH net-next 6/7] net: ll_temac: move trailing statements to next line Haoyue Xu
2022-09-17 10:38 ` [PATCH net-next 7/7] net: ll_temac: axienet: delete unnecessary blank lines and spaces Haoyue Xu
2022-09-20 5:30 ` [PATCH net-next 0/7] net: ll_temac: Cleanup for clearing static warnings Harini Katakam
2022-09-22 1:40 ` 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=166381081697.5452.7754102556865331552.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=huangdaode@huawei.com \
--cc=huangjunxian6@hisilicon.com \
--cc=kuba@kernel.org \
--cc=liangwenpeng@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=liyangyang20@huawei.com \
--cc=michal.simek@xilinx.com \
--cc=netdev@vger.kernel.org \
--cc=xuhaoyue1@hisilicon.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