From: patchwork-bot+netdevbpf@kernel•org
To: Lorenzo Bianconi <lorenzo@kernel•org>
Cc: netdev@vger•kernel.org, davem@davemloft•net, edumazet@google•com,
kuba@kernel•org, pabeni@redhat•com, lorenzo.bianconi@redhat•com,
nbd@nbd•name, john@phrozen•org, sean.wang@mediatek•com,
Mark-MC.Lee@mediatek•com, sujuan.chen@mediatek•com,
daniel@makrotopia•org, leon@kernel•org,
alexander.duyck@gmail•com
Subject: Re: [PATCH v6 net-next 0/5] net: ethernet: mtk_wed: introduce reset support
Date: Tue, 17 Jan 2023 10:50:17 +0000 [thread overview]
Message-ID: <167395261720.2304.3313123106989727184.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1673715298.git.lorenzo@kernel.org>
Hello:
This series was applied to netdev/net-next.git (master)
by Paolo Abeni <pabeni@redhat•com>:
On Sat, 14 Jan 2023 18:01:27 +0100 you wrote:
> Introduce proper reset integration between ethernet and wlan drivers in order
> to schedule wlan driver reset when ethernet/wed driver is resetting.
> Introduce mtk_hw_reset_monitor work in order to detect possible DMA hangs.
>
> Changes since v5:
> - log error reported by reset callback
> - convert reset_complete callback from int to void
>
> [...]
Here is the summary with links:
- [v6,net-next,1/5] net: ethernet: mtk_eth_soc: introduce mtk_hw_reset utility routine
https://git.kernel.org/netdev/net-next/c/bccd19bce0b6
- [v6,net-next,2/5] net: ethernet: mtk_eth_soc: introduce mtk_hw_warm_reset support
https://git.kernel.org/netdev/net-next/c/a9724b9c477f
- [v6,net-next,3/5] net: ethernet: mtk_eth_soc: align reset procedure to vendor sdk
https://git.kernel.org/netdev/net-next/c/06127504c282
- [v6,net-next,4/5] net: ethernet: mtk_eth_soc: add dma checks to mtk_hw_reset_check
https://git.kernel.org/netdev/net-next/c/93b2591ad0d0
- [v6,net-next,5/5] net: ethernet: mtk_wed: add reset/reset_complete callbacks
https://git.kernel.org/netdev/net-next/c/08a764a7c51b
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-01-17 10:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-14 17:01 [PATCH v6 net-next 0/5] net: ethernet: mtk_wed: introduce reset support Lorenzo Bianconi
2023-01-14 17:01 ` [PATCH v6 net-next 1/5] net: ethernet: mtk_eth_soc: introduce mtk_hw_reset utility routine Lorenzo Bianconi
2023-01-14 17:01 ` [PATCH v6 net-next 2/5] net: ethernet: mtk_eth_soc: introduce mtk_hw_warm_reset support Lorenzo Bianconi
2023-01-14 17:01 ` [PATCH v6 net-next 3/5] net: ethernet: mtk_eth_soc: align reset procedure to vendor sdk Lorenzo Bianconi
2023-01-14 17:01 ` [PATCH v6 net-next 4/5] net: ethernet: mtk_eth_soc: add dma checks to mtk_hw_reset_check Lorenzo Bianconi
2023-01-14 17:01 ` [PATCH v6 net-next 5/5] net: ethernet: mtk_wed: add reset/reset_complete callbacks Lorenzo Bianconi
2023-01-17 10:50 ` 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=167395261720.2304.3313123106989727184.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel$(echo .)org \
--cc=Mark-MC.Lee@mediatek$(echo .)com \
--cc=alexander.duyck@gmail$(echo .)com \
--cc=daniel@makrotopia$(echo .)org \
--cc=davem@davemloft$(echo .)net \
--cc=edumazet@google$(echo .)com \
--cc=john@phrozen$(echo .)org \
--cc=kuba@kernel$(echo .)org \
--cc=leon@kernel$(echo .)org \
--cc=lorenzo.bianconi@redhat$(echo .)com \
--cc=lorenzo@kernel$(echo .)org \
--cc=nbd@nbd$(echo .)name \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(echo .)com \
--cc=sean.wang@mediatek$(echo .)com \
--cc=sujuan.chen@mediatek$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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