From: patchwork-bot+netdevbpf@kernel.org
To: Zhengchao Shao <shaozhengchao@huawei.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, j.vosburgh@gmail.com,
andy@greyhouse.net, weiyongjun1@huawei.com,
yuehaibing@huawei.com, liuhangbin@gmail.com,
vadim.fedorenko@linux.dev
Subject: Re: [PATCH net-next,v2 0/5] bonding: do some cleanups in bond driver
Date: Fri, 11 Aug 2023 10:20:29 +0000 [thread overview]
Message-ID: <169174922998.9362.12886233325863357951.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230810135007.3834770-1-shaozhengchao@huawei.com>
Hello:
This series was applied to netdev/net-next.git (main)
by David S. Miller <davem@davemloft.net>:
On Thu, 10 Aug 2023 21:50:02 +0800 you wrote:
> Do some cleanups in bond driver.
>
> ---
> v2: use IS_ERR instead of NULL check in patch 2/5, update commit
> information in patch 3/5, remove inline modifier in patch 4/5
> ---
> Zhengchao Shao (5):
> bonding: add modifier to initialization function and exit function
> bonding: use IS_ERR instead of NULL check in bond_create_debugfs
> bonding: remove redundant NULL check in debugfs function
> bonding: use bond_set_slave_arr to simplify code
> bonding: remove unnecessary NULL check in bond_destructor
>
> [...]
Here is the summary with links:
- [net-next,v2,1/5] bonding: add modifier to initialization function and exit function
https://git.kernel.org/netdev/net-next/c/e08190ef514f
- [net-next,v2,2/5] bonding: use IS_ERR instead of NULL check in bond_create_debugfs
https://git.kernel.org/netdev/net-next/c/57647e6fdf17
- [net-next,v2,3/5] bonding: remove redundant NULL check in debugfs function
https://git.kernel.org/netdev/net-next/c/cc317ea3d927
- [net-next,v2,4/5] bonding: use bond_set_slave_arr to simplify code
https://git.kernel.org/netdev/net-next/c/a8f3f4b44845
- [net-next,v2,5/5] bonding: remove unnecessary NULL check in bond_destructor
https://git.kernel.org/netdev/net-next/c/f5370ba3590d
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:[~2023-08-11 10:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-10 13:50 [PATCH net-next,v2 0/5] bonding: do some cleanups in bond driver Zhengchao Shao
2023-08-10 13:50 ` [PATCH net-next,v2 1/5] bonding: add modifier to initialization function and exit function Zhengchao Shao
2023-08-10 13:50 ` [PATCH net-next,v2 2/5] bonding: use IS_ERR instead of NULL check in bond_create_debugfs Zhengchao Shao
2023-08-10 13:50 ` [PATCH net-next,v2 3/5] bonding: remove redundant NULL check in debugfs function Zhengchao Shao
2023-08-10 13:50 ` [PATCH net-next,v2 4/5] bonding: use bond_set_slave_arr to simplify code Zhengchao Shao
2023-08-10 13:50 ` [PATCH net-next,v2 5/5] bonding: remove unnecessary NULL check in bond_destructor Zhengchao Shao
2023-08-11 6:04 ` [PATCH net-next,v2 0/5] bonding: do some cleanups in bond driver Hangbin Liu
2023-08-11 10:20 ` 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=169174922998.9362.12886233325863357951.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andy@greyhouse.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=j.vosburgh@gmail.com \
--cc=kuba@kernel.org \
--cc=liuhangbin@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shaozhengchao@huawei.com \
--cc=vadim.fedorenko@linux.dev \
--cc=weiyongjun1@huawei.com \
--cc=yuehaibing@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox