From: patchwork-bot+netdevbpf@kernel.org
To: Daniel Golle <daniel@makrotopia.org>
Cc: kuba@kernel.org, linux-mediatek@lists.infradead.org,
netdev@vger.kernel.org, lorenzo@kernel.org,
sujuan.chen@mediatek.com, Bo.Jiao@mediatek.com, nbd@nbd.name,
john@phrozen.org, sean.wang@mediatek.com,
Mark-MC.Lee@mediatek.com, davem@davemloft.net,
edumazet@google.com, pabeni@redhat.com, matthias.bgg@gmail.com,
ptpt52@gmail.com, thomas.huehn@hs-nordhausen.de
Subject: Re: [PATCH v2] net: ethernet: mtk_eth_soc: fix state in __mtk_foe_entry_clear
Date: Sat, 01 Oct 2022 02:20:23 +0000 [thread overview]
Message-ID: <166459082399.26825.7869128536663169925.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <YzY+1Yg0FBXcnrtc@makrotopia.org>
Hello:
This patch was applied to netdev/net.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Fri, 30 Sep 2022 01:56:53 +0100 you wrote:
> Setting ib1 state to MTK_FOE_STATE_UNBIND in __mtk_foe_entry_clear
> routine as done by commit 0e80707d94e4c8 ("net: ethernet: mtk_eth_soc:
> fix typo in __mtk_foe_entry_clear") breaks flow offloading, at least
> on older MTK_NETSYS_V1 SoCs, OpenWrt users have confirmed the bug on
> MT7622 and MT7621 systems.
> Felix Fietkau suggested to use MTK_FOE_STATE_INVALID instead which
> works well on both, MTK_NETSYS_V1 and MTK_NETSYS_V2.
>
> [...]
Here is the summary with links:
- [v2] net: ethernet: mtk_eth_soc: fix state in __mtk_foe_entry_clear
https://git.kernel.org/netdev/net/c/ae3ed15da588
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2022-10-01 2:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-28 1:25 [PATCH] net: ethernet: mtk_eth_soc: fix state in __mtk_foe_entry_clear Daniel Golle
2022-09-28 9:27 ` Lorenzo Bianconi
2022-09-29 2:09 ` Jakub Kicinski
2022-09-30 0:56 ` [PATCH v2] " Daniel Golle
2022-10-01 2:20 ` patchwork-bot+netdevbpf [this message]
2022-10-03 12:59 ` [PATCH v2] net: ethernet: mtk_eth_soc: fix state in __mtk_foe_entry_clear: manual merge Matthieu Baerts
2022-10-03 13:47 ` Daniel Golle
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=166459082399.26825.7869128536663169925.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=Bo.Jiao@mediatek.com \
--cc=Mark-MC.Lee@mediatek.com \
--cc=daniel@makrotopia.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=john@phrozen.org \
--cc=kuba@kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=lorenzo@kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=nbd@nbd.name \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=ptpt52@gmail.com \
--cc=sean.wang@mediatek.com \
--cc=sujuan.chen@mediatek.com \
--cc=thomas.huehn@hs-nordhausen.de \
/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.