From: syzbot ci <syzbot+cie83dda8cdc358949@syzkaller.appspotmail.com>
To: syzkaller-upstream-moderation@googlegroups.com
Cc: syzbot@lists.linux.dev
Subject: [moderation/CI] Re: Use the QMI service IDs from the QMI header
Date: Mon, 16 Mar 2026 14:39:58 -0700 [thread overview]
Message-ID: <69b878ae.050a0220.248e02.011d.GAE@google.com> (raw)
syzbot ci has tested the following series
[v2] Use the QMI service IDs from the QMI header
https://lore.kernel.org/all/20260316171419.2619620-1-daniel.lezcano@oss.qualcomm.com
* [PATCH v2 1/4] net: ipa: Use the unified QMI service ID instead of defining it locally
* [PATCH v2 2/4] wifi: ath: Use the unified QMI service ID instead of defining it locally
* [PATCH v2 3/4] slimbus: qcom-ngd-ctrl: Use the unified QMI service ID instead of defining it locally
* [PATCH v2 4/4] ALSA: usb-audio: qcom: Use the unified QMI service ID instead of defining it locally
and found the following issue:
kernel build error
Full report is available here:
https://ci.syzbot.org/series/a7a585ab-172d-40a0-ba91-1886887daddf
***
kernel build error
tree: net-next
URL: https://kernel.googlesource.com/pub/scm/linux/kernel/git/netdev/net-next.git
base: 97e4567d39941248579da34b7fbb568e6659511e
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/c4068879-f990-4c0a-9fec-fd918102a7e1/config
drivers/net/wireless/ath/ath11k/qmi.c:3340:40: error: use of undeclared identifier 'QMI_SERVICE_ID_WLFW'
***
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.
The email will later be sent to:
[andersson@kernel.org andrew@lunn.ch arnd@arndb.de ath10k@lists.infradead.org ath11k@lists.infradead.org ath12k@lists.infradead.org broonie@kernel.org dan.carpenter@linaro.org daniel.lezcano@oss.qualcomm.com davem@davemloft.net dmitry.baryshkov@oss.qualcomm.com edumazet@google.com elder@kernel.org gregkh@linuxfoundation.org jjohnson@kernel.org kees@kernel.org konradybcio@kernel.org kuba@kernel.org linux-arm-msm@vger.kernel.org linux-kernel@vger.kernel.org linux-remoteproc@vger.kernel.org linux-sound@vger.kernel.org linux-wireless@vger.kernel.org mathieu.poirier@linaro.org netdev@vger.kernel.org pabeni@redhat.com perex@perex.cz quic_wcheng@quicinc.com srini@kernel.org tiwai@suse.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-03-16 21:39 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=69b878ae.050a0220.248e02.011d.GAE@google.com \
--to=syzbot+cie83dda8cdc358949@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 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.