From: Felix Fietkau <nbd@nbd.name>
To: Shengyu Qu <wiagn233@outlook.com>,
Ping-Ke Shih <pkshih@realtek.com>,
"lorenzo@kernel.org" <lorenzo@kernel.org>,
"ryder.lee@mediatek.com" <ryder.lee@mediatek.com>,
"shayne.chen@mediatek.com" <shayne.chen@mediatek.com>,
"sean.wang@mediatek.com" <sean.wang@mediatek.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-mediatek@lists.infradead.org"
<linux-mediatek@lists.infradead.org>
Cc: "johannes@sipsolutions.net" <johannes@sipsolutions.net>,
"matthias.bgg@gmail.com" <matthias.bgg@gmail.com>,
"angelogioacchino.delregno@collabora.com"
<angelogioacchino.delregno@collabora.com>,
Peter Chiu <chui-hao.chiu@mediatek.com>
Subject: Re: [PATCH v1] mt76: mt7915: wed: find rx token by physical address
Date: Thu, 13 Mar 2025 13:47:16 +0100 [thread overview]
Message-ID: <0ab3fb92-b529-46a3-bc78-230eaf4ae805@nbd.name> (raw)
In-Reply-To: <TYCPR01MB843770121E6576BB3807CD0A98D32@TYCPR01MB8437.jpnprd01.prod.outlook.com>
On 13.03.25 13:43, Shengyu Qu wrote:
> Hi Felix,
>
> I'm not sure about the token ID incorrect frequency, this is just a port
> of downstream patch, sorry.
Can you reproduce the issue that the downstream patch supposedly fixes?
If so, you could add some printk to check how frequently it occurs.
- Felix
next prev parent reply other threads:[~2025-03-13 12:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-22 11:38 Shengyu Qu
2025-03-11 8:51 ` Shengyu Qu
2025-03-12 1:41 ` Ping-Ke Shih
2025-03-12 9:09 ` Felix Fietkau
2025-03-13 12:43 ` Shengyu Qu
2025-03-13 12:47 ` Felix Fietkau [this message]
2025-03-13 13:09 ` Shengyu Qu
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=0ab3fb92-b529-46a3-bc78-230eaf4ae805@nbd.name \
--to=nbd@nbd.name \
--cc=angelogioacchino.delregno@collabora.com \
--cc=chui-hao.chiu@mediatek.com \
--cc=johannes@sipsolutions.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=lorenzo@kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=pkshih@realtek.com \
--cc=ryder.lee@mediatek.com \
--cc=sean.wang@mediatek.com \
--cc=shayne.chen@mediatek.com \
--cc=wiagn233@outlook.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®