From: Leon Romanovsky <leon@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
Subject: Re: [PATCH net-next 5/5] bonding: remove unnecessary NULL check in bond_destructor
Date: Sun, 13 Aug 2023 10:58:00 +0300 [thread overview]
Message-ID: <20230813075800.GC7707@unreal> (raw)
In-Reply-To: <20230809124107.360574-6-shaozhengchao@huawei.com>
On Wed, Aug 09, 2023 at 08:41:07PM +0800, Zhengchao Shao wrote:
> The free_percpu function also could check whether "rr_tx_counter"
> parameter is NULL. Therefore, remove NULL check in bond_destructor.
>
> Signed-off-by: Zhengchao Shao <shaozhengchao@huawei.com>
> ---
> drivers/net/bonding/bond_main.c | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
Thanks,
Reviewed-by: Leon Romanovsky <leonro@nvidia.com>
prev parent reply other threads:[~2023-08-13 7:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-09 12:41 [PATCH net-next 0/5] bonding: do some cleanups in bond driver Zhengchao Shao
2023-08-09 12:41 ` [PATCH net-next 1/5] bonding: add modifier to initialization function and exit function Zhengchao Shao
2023-08-13 7:57 ` Leon Romanovsky
2023-08-09 12:41 ` [PATCH net-next 2/5] bonding: remove warning printing in bond_create_debugfs Zhengchao Shao
2023-08-10 2:53 ` Hangbin Liu
2023-08-10 8:06 ` shaozhengchao
2023-08-09 12:41 ` [PATCH net-next 3/5] bonding: remove unnecessary NULL check in debugfs function Zhengchao Shao
2023-08-09 16:13 ` Jay Vosburgh
2023-08-10 3:08 ` Hangbin Liu
2023-08-10 8:08 ` shaozhengchao
2023-08-09 12:41 ` [PATCH net-next 4/5] bonding: use bond_set_slave_arr to simplify code Zhengchao Shao
2023-08-10 0:17 ` Vadim Fedorenko
2023-08-10 8:10 ` shaozhengchao
2023-08-09 12:41 ` [PATCH net-next 5/5] bonding: remove unnecessary NULL check in bond_destructor Zhengchao Shao
2023-08-13 7:58 ` Leon Romanovsky [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=20230813075800.GC7707@unreal \
--to=leon@kernel.org \
--cc=andy@greyhouse.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=j.vosburgh@gmail.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shaozhengchao@huawei.com \
--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 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.