From: syzbot ci <syzbot+ci03289160ae271a01@syzkaller.appspotmail.com>
To: syzkaller-upstream-moderation@googlegroups.com
Cc: syzbot@lists.linux.dev
Subject: [moderation/CI] Re: wifi: mt76: mt7925: add MT7928 debugfs txpower_sku with power table selection
Date: Sat, 25 Jul 2026 06:32:03 -0700 [thread overview]
Message-ID: <6a64bad3.70955b6c.323240.001e.GAE@google.com> (raw)
syzbot ci has tested the following series
[v1] wifi: mt76: mt7925: add MT7928 debugfs txpower_sku with power table selection
https://lore.kernel.org/all/20260724085202.3156422-1-jb.tsai@mediatek.com
* [PATCH] wifi: mt76: mt7925: add MT7928 debugfs txpower_sku with power table selection
and found the following issue:
kernel build error
Full report is available here:
https://ci.syzbot.org/series/902de955-db8d-47e0-a4fe-d624ae5adeb5
***
kernel build error
tree: wireless-next
URL: https://kernel.googlesource.com/pub/scm/linux/kernel/git/wireless/wireless-next.git
base: 90883c513ca01e77c56b8d94be7de11420c1dacf
arch: amd64
compiler: Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8
config: https://ci.syzbot.org/builds/3bcd1859-e29d-4361-b72c-e2c7e47081ee/config
drivers/net/wireless/mediatek/mt76/mt7925/debugfs.c:445:6: error: call to undeclared function 'is_mt7928'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
***
If these findings have caused you to resend the series or submit a
separate fix, please add the following tag to your commit message:
Tested-by: syzbot@syzkaller.appspotmail.com
---
This report is generated by a bot. It may contain errors.
syzbot ci engineers can be reached at syzkaller@googlegroups.com.
To test a patch for this bug, please reply with `#syz test`
(should be on a separate line).
The patch should be attached to the email.
Note: arguments like custom git repos and branches are not supported.
The email will later be sent to:
[charlie-cy.wu@mediatek.com jb.tsai@mediatek.com linux-mediatek@lists.infradead.org linux-wireless@vger.kernel.org litien.chang@mediatek.com lorenzo@kernel.org nbd@nbd.name quan.zhou@mediatek.com ryder.lee@mediatek.com sean.wang@mediatek.com]
If the report looks fine to you, reply with:
#syz upstream
If the report is a false positive, reply with
#syz invalid
reply other threads:[~2026-07-25 13:32 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=6a64bad3.70955b6c.323240.001e.GAE@google.com \
--to=syzbot+ci03289160ae271a01@syzkaller.appspotmail.com \
--cc=syzbot@lists.linux.dev \
--cc=syzkaller-upstream-moderation@googlegroups.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