From: patchwork-bot+netdevbpf@kernel.org
To: Baokun Li <libaokun1@huawei.com>
Cc: linux-kernel@vger.kernel.org, simon.horman@corigine.com,
davem@davemloft.net, kuba@kernel.org, weiyongjun1@huawei.com,
yuehaibing@huawei.com, yangjihong1@huawei.com,
yukuai3@huawei.com, oss-drivers@corigine.com,
netdev@vger.kernel.org, kernel-janitors@vger.kernel.org,
hulkci@huawei.com
Subject: Re: [PATCH net-next v2] nfp: use list_move instead of list_del/list_add in nfp_cppcore.c
Date: Wed, 09 Jun 2021 21:10:04 +0000 [thread overview]
Message-ID: <162327300453.16455.10765731568023013877.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210609070921.1330407-1-libaokun1@huawei.com>
Hello:
This patch was applied to netdev/net-next.git (refs/heads/master):
On Wed, 9 Jun 2021 15:09:21 +0800 you wrote:
> Using list_move() instead of list_del() + list_add() in nfp_cppcore.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] nfp: use list_move instead of list_del/list_add in nfp_cppcore.c
https://git.kernel.org/netdev/net-next/c/39c3783ec062
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: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-09 7:09 [PATCH net-next v2] nfp: use list_move instead of list_del/list_add in nfp_cppcore.c Baokun Li
2021-06-09 8:58 ` Simon Horman
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=162327300453.16455.10765731568023013877.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=hulkci@huawei.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=kuba@kernel.org \
--cc=libaokun1@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=oss-drivers@corigine.com \
--cc=simon.horman@corigine.com \
--cc=weiyongjun1@huawei.com \
--cc=yangjihong1@huawei.com \
--cc=yuehaibing@huawei.com \
--cc=yukuai3@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;
as well as URLs for NNTP newsgroup(s).