From: syzbot ci <syzbot+ci33b6c2303971f18f@syzkaller.appspotmail.com>
To: syzkaller-upstream-moderation@googlegroups.com
Cc: syzbot@lists.linux.dev
Subject: [moderation/CI] Re: EML Capabilities compliance changes
Date: Tue, 14 Apr 2026 04:15:31 -0700 [thread overview]
Message-ID: <69de21d3.a00a0220.468cb.005e.GAE@google.com> (raw)
syzbot ci has tested the following series
[v2] EML Capabilities compliance changes
https://lore.kernel.org/all/20260409135035.4018725-1-pmartin-gomez@freebox.fr
* [PATCH v2 1/4] wifi: Remove invalid 128TU transition timeout constant
* [PATCH v2 2/4] wifi: Remove EMLMR Delay subfield definitions
* [PATCH v2 3/4] wifi: Rename EMLSR delay constants and add EMLMR helpers and definitions
* [PATCH v2 4/4] wifi: Update EML function documentation to remove EMLSR-specific references
and found the following issue:
kernel build error
Full report is available here:
https://ci.syzbot.org/series/967a3c8a-f52b-456f-ba2d-fc09cb006ba9
***
kernel build error
tree: linux-next
URL: https://kernel.googlesource.com/pub/scm/linux/kernel/git/next/linux-next
base: 709503c4a2102b32de4b4e64687df86503c74eba
arch: amd64
compiler: Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8
config: https://ci.syzbot.org/builds/0de3eafc-c510-49f5-b272-35bc499d3d4f/config
./include/linux/ieee80211-eht.h:1138:18: error: use of undeclared identifier 'IEEE80211_EML_CAP_EMLSR_PADDING_DELAY_256US'
./include/linux/ieee80211-eht.h:1188:25: error: use of undeclared identifier 'IEEE80211_EML_CAP_EMLMR_SUPP'
./include/linux/ieee80211-eht.h:1200:18: error: use of undeclared identifier 'IEEE80211_EML_CAP_EMLMR_PADDING_DELAY_256US'
./include/linux/ieee80211-eht.h:1218:25: error: use of undeclared identifier 'IEEE80211_EML_CAP_EMLMR_SUPP'
***
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:
[johannes@sipsolutions.net linux-wireless@vger.kernel.org pmartin-gomez@freebox.fr]
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-04-14 11:15 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=69de21d3.a00a0220.468cb.005e.GAE@google.com \
--to=syzbot+ci33b6c2303971f18f@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