From: patchwork-bot+netdevbpf@kernel.org
To: Baokun Li <libaokun1@huawei.com>
Cc: linux-kernel@vger.kernel.org, yisen.zhuang@huawei.com,
salil.mehta@huawei.com, davem@davemloft.net, kuba@kernel.org,
tanhuazhong@huawei.com, huangguangbin2@huawei.com,
shenjian15@huawei.com, moyufeng@huawei.com,
liaoguojia@huawei.com, zhangjiaran@huawei.com,
weiyongjun1@huawei.com, yuehaibing@huawei.com,
yangjihong1@huawei.com, yukuai3@huawei.com,
netdev@vger.kernel.org, kernel-janitors@vger.kernel.org,
hulkci@huawei.com
Subject: Re: [PATCH net-next v2] net: hns3: use list_move_tail instead of list_del/list_add_tail in hclgevf_main.c
Date: Wed, 09 Jun 2021 21:10:04 +0000 [thread overview]
Message-ID: <162327300448.16455.2233743264153091413.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210609071720.1346684-1-libaokun1@huawei.com>
Hello:
This patch was applied to netdev/net-next.git (refs/heads/master):
On Wed, 9 Jun 2021 15:17:20 +0800 you wrote:
> Using list_move_tail() instead of list_del() + list_add_tail() in hclgevf_main.c.
>
> Reported-by: Hulk Robot <hulkci@huawei.com>
> Signed-off-by: Baokun Li <libaokun1@huawei.com>
> ---
> V1->V2:
> CC mailist
>
> [...]
Here is the summary with links:
- [net-next,v2] net: hns3: use list_move_tail instead of list_del/list_add_tail in hclgevf_main.c
https://git.kernel.org/netdev/net-next/c/49768ce98c2c
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-06-09 21:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-09 7:17 [PATCH net-next v2] net: hns3: use list_move_tail instead of list_del/list_add_tail in hclgevf_main.c Baokun Li
2021-06-09 21:10 ` 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=162327300448.16455.2233743264153091413.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=huangguangbin2@huawei.com \
--cc=hulkci@huawei.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=kuba@kernel.org \
--cc=liaoguojia@huawei.com \
--cc=libaokun1@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=moyufeng@huawei.com \
--cc=netdev@vger.kernel.org \
--cc=salil.mehta@huawei.com \
--cc=shenjian15@huawei.com \
--cc=tanhuazhong@huawei.com \
--cc=weiyongjun1@huawei.com \
--cc=yangjihong1@huawei.com \
--cc=yisen.zhuang@huawei.com \
--cc=yuehaibing@huawei.com \
--cc=yukuai3@huawei.com \
--cc=zhangjiaran@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.