From: patchwork-bot+netdevbpf@kernel.org
To: Li Zetao <lizetao1@huawei.com>
Cc: ioana.ciornei@nxp.com, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, netdev@vger.kernel.org
Subject: Re: [PATCH net-next 0/2] net: Remove redundant initialization owner
Date: Tue, 08 Aug 2023 02:30:22 +0000 [thread overview]
Message-ID: <169146182265.15123.6784529323477269174.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230804095946.99956-1-lizetao1@huawei.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Fri, 4 Aug 2023 17:59:44 +0800 you wrote:
> This patch set removes redundant initialization owner when register a
> fsl_mc_driver driver
>
> Li Zetao (2):
> net: dpaa2-eth: Remove redundant initialization owner in
> dpaa2_eth_driver
> net: dpaa2-switch: Remove redundant initialization owner in
> dpaa2_switch_drv
>
> [...]
Here is the summary with links:
- [net-next,1/2] net: dpaa2-eth: Remove redundant initialization owner in dpaa2_eth_driver
https://git.kernel.org/netdev/net-next/c/43265d3fceeb
- [net-next,2/2] net: dpaa2-switch: Remove redundant initialization owner in dpaa2_switch_drv
https://git.kernel.org/netdev/net-next/c/ca46d207c972
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-08 2:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-04 9:59 [PATCH net-next 0/2] net: Remove redundant initialization owner Li Zetao
2023-08-04 9:59 ` [PATCH net-next 1/2] net: dpaa2-eth: Remove redundant initialization owner in dpaa2_eth_driver Li Zetao
2023-08-04 9:59 ` [PATCH net-next 2/2] net: dpaa2-switch: Remove redundant initialization owner in dpaa2_switch_drv Li Zetao
2023-08-05 11:38 ` [PATCH net-next 0/2] net: Remove redundant initialization owner Simon Horman
2023-08-08 2:30 ` 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=169146182265.15123.6784529323477269174.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=ioana.ciornei@nxp.com \
--cc=kuba@kernel.org \
--cc=lizetao1@huawei.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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.