From: patchwork-bot+netdevbpf@kernel.org
To: Lorenzo Bianconi <lorenzo@kernel.org>
Cc: netdev@vger.kernel.org, nbd@nbd.name, john@phrozen.org,
sean.wang@mediatek.com, Mark-MC.Lee@mediatek.com,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, lorenzo.bianconi@redhat.com,
sujuan.chen@mediatek.com, linux-mediatek@lists.infradead.org
Subject: Re: [PATCH v2 net-next 0/5] refactor mtk_wed code to introduce SER support
Date: Tue, 29 Nov 2022 10:50:15 +0000 [thread overview]
Message-ID: <166971901588.19778.10630700860391594929.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1669303154.git.lorenzo@kernel.org>
Hello:
This series was applied to netdev/net-next.git (master)
by Paolo Abeni <pabeni@redhat.com>:
On Thu, 24 Nov 2022 16:22:50 +0100 you wrote:
> Refactor mtk_wed support in order to introduce proper integration for hw reset
> between mtk_eth_soc/mtk_wed and mt76 drivers.
>
> Changes since v1:
> - improve commit logs
>
> Lorenzo Bianconi (5):
> net: ethernet: mtk_wed: return status value in mtk_wdma_rx_reset
> net: ethernet: mtk_wed: move MTK_WDMA_RESET_IDX_TX configuration in
> mtk_wdma_tx_reset
> net: ethernet: mtk_wed: update mtk_wed_stop
> net: ethernet: mtk_wed: add mtk_wed_rx_reset routine
> net: ethernet: mtk_wed: add reset to tx_ring_setup callback
>
> [...]
Here is the summary with links:
- [v2,net-next,1/5] net: ethernet: mtk_wed: return status value in mtk_wdma_rx_reset
https://git.kernel.org/netdev/net-next/c/b0488c4598a5
- [v2,net-next,2/5] net: ethernet: mtk_wed: move MTK_WDMA_RESET_IDX_TX configuration in mtk_wdma_tx_reset
https://git.kernel.org/netdev/net-next/c/92b1169660eb
- [v2,net-next,3/5] net: ethernet: mtk_wed: update mtk_wed_stop
https://git.kernel.org/netdev/net-next/c/f78cd9c783e0
- [v2,net-next,4/5] net: ethernet: mtk_wed: add mtk_wed_rx_reset routine
https://git.kernel.org/netdev/net-next/c/b08134c6e109
- [v2,net-next,5/5] net: ethernet: mtk_wed: add reset to tx_ring_setup callback
https://git.kernel.org/netdev/net-next/c/23dca7a90017
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:[~2022-11-29 10:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-24 15:22 [PATCH v2 net-next 0/5] refactor mtk_wed code to introduce SER support Lorenzo Bianconi
2022-11-24 15:22 ` [PATCH v2 net-next 1/5] net: ethernet: mtk_wed: return status value in mtk_wdma_rx_reset Lorenzo Bianconi
2022-11-24 15:22 ` [PATCH v2 net-next 2/5] net: ethernet: mtk_wed: move MTK_WDMA_RESET_IDX_TX configuration in mtk_wdma_tx_reset Lorenzo Bianconi
2022-11-24 15:22 ` [PATCH v2 net-next 3/5] net: ethernet: mtk_wed: update mtk_wed_stop Lorenzo Bianconi
2022-11-24 15:22 ` [PATCH v2 net-next 4/5] net: ethernet: mtk_wed: add mtk_wed_rx_reset routine Lorenzo Bianconi
2022-11-24 15:22 ` [PATCH v2 net-next 5/5] net: ethernet: mtk_wed: add reset to tx_ring_setup callback Lorenzo Bianconi
2022-11-29 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=166971901588.19778.10630700860391594929.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=Mark-MC.Lee@mediatek.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=john@phrozen.org \
--cc=kuba@kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=lorenzo.bianconi@redhat.com \
--cc=lorenzo@kernel.org \
--cc=nbd@nbd.name \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sean.wang@mediatek.com \
--cc=sujuan.chen@mediatek.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.