From: Lorenzo Bianconi <lorenzo@kernel•org>
To: Jakub Kicinski <kuba@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, pabeni@redhat•com,
pablo@netfilter•org, matthias.bgg@gmail•com,
linux-mediatek@lists•infradead.org, lorenzo.bianconi@redhat•com,
Ryder.Lee@mediatek•com, Evelyn.Tsai@mediatek•com
Subject: Re: [PATCH net-next] net: ethernet: mtk-ppe: fix traffic offload with bridged wlan
Date: Wed, 20 Jul 2022 09:45:13 +0200 [thread overview]
Message-ID: <YteyiWvRGSRAeAIJ@localhost.localdomain> (raw)
In-Reply-To: <20220719174038.7ee25c6d@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 876 bytes --]
> On Mon, 18 Jul 2022 20:36:39 +0200 Lorenzo Bianconi wrote:
> > A typical flow offload scenario for OpenWrt users is routed traffic
> > received by the wan interface that is redirected to a wlan device
> > belonging to the lan bridge. Current implementation fails to
> > fill wdma offload info in mtk_flow_get_wdma_info() since odev device is
> > the local bridge. Fix the issue running dev_fill_forward_path routine in
> > mtk_flow_get_wdma_info in order to identify the wlan device.
>
> AFAIU this will conflict with 53eb9b04560c ("net: ethernet: mtk_ppe:
> fix possible NULL pointer dereference in mtk_flow_get_wdma_info")?
> We merge net -> net-next every Thu, please wait for that to happen
> and then repost. Conflicting patches are extra work for Stephen and
> for me.
ack, right, sorry for that. I will repost after the merge.
Regards,
Lorenzo
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
prev parent reply other threads:[~2022-07-20 7:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-18 18:36 [PATCH net-next] net: ethernet: mtk-ppe: fix traffic offload with bridged wlan Lorenzo Bianconi
2022-07-20 0:40 ` Jakub Kicinski
2022-07-20 7:45 ` Lorenzo Bianconi [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=YteyiWvRGSRAeAIJ@localhost.localdomain \
--to=lorenzo@kernel$(echo .)org \
--cc=Evelyn.Tsai@mediatek$(echo .)com \
--cc=Mark-MC.Lee@mediatek$(echo .)com \
--cc=Ryder.Lee@mediatek$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=edumazet@google$(echo .)com \
--cc=john@phrozen$(echo .)org \
--cc=kuba@kernel$(echo .)org \
--cc=linux-mediatek@lists$(echo .)infradead.org \
--cc=lorenzo.bianconi@redhat$(echo .)com \
--cc=matthias.bgg@gmail$(echo .)com \
--cc=nbd@nbd$(echo .)name \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(echo .)com \
--cc=pablo@netfilter$(echo .)org \
--cc=sean.wang@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