All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot ci <syzbot+ci65ba89adbec7a7b3@syzkaller.appspotmail.com>
To: syzkaller-upstream-moderation@googlegroups.com
Cc: syzbot@lists.linux.dev
Subject: [moderation/CI] Re: Add support for IPQ5018 Bluetooth
Date: Mon, 29 Jun 2026 07:46:15 -0700	[thread overview]
Message-ID: <6a428537.854d4ab9.360e1d.0009.GAE@google.com> (raw)

syzbot ci has tested the following series

[v2] Add support for IPQ5018 Bluetooth
https://lore.kernel.org/all/20260629-ipq5018-bluetooth-v2-0-02770f03b6bb@outlook.com
* [PATCH v2 1/6] dt-bindings: net: bluetooth: Document Qualcomm IPQ5018 Bluetooth controller
* [PATCH v2 2/6] Bluetooth: btqca: Add IPQ5018 support
* [PATCH v2 3/6] firmware: qcom: scm: Add support for setting Bluetooth power modes
* [PATCH v2 4/6] Bluetooth: Introduce Qualcomm IPQ5018 IPC based HCI driver
* [PATCH v2 5/6] arm64: dts: qcom: ipq5018: add nodes required for Bluetooth support
* [PATCH v2 6/6] MAINTAINERS: Add entry for Qualcomm IPQ5018 Bluetooth driver

and found the following issue:
kernel build error

Full report is available here:
https://ci.syzbot.org/series/11239a4c-1917-4b73-8aa0-02496635d8f0

***

kernel build error

tree:      net-next
URL:       https://kernel.googlesource.com/pub/scm/linux/kernel/git/netdev/net-next.git
base:      805185b7c7a1069e407b6f7b3bc98e44d415f484
arch:      amd64
compiler:  Debian clang version 22.1.6 (++20260514074242+fc4aad7b5db3-1~exp1~20260514074407.73), Debian LLD 22.1.6
config:    https://ci.syzbot.org/builds/0806f9ab-e49e-4caa-8ade-1b3c22d09a60/config

drivers/bluetooth/btqcomipc.c:316:9: error: call to undeclared function 'FIELD_PREP'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
drivers/bluetooth/btqcomipc.c:516:14: error: call to undeclared function 'FIELD_GET'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
drivers/bluetooth/btqcomipc.c:681:8: error: call to undeclared function 'qcom_mdt_pas_init'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
drivers/bluetooth/btqcomipc.c:812:54: error: too few arguments to function call, expected 6, have 5
drivers/bluetooth/btqcomipc.c:821:22: error: use of undeclared identifier 'HCI_QUIRK_USE_BDADDR_NVMEM'; did you mean 'HCI_QUIRK_USE_BDADDR_PROPERTY'?
drivers/bluetooth/btqcomipc.c:822:22: error: use of undeclared identifier 'HCI_QUIRK_BDADDR_NVMEM_BE'
drivers/bluetooth/btqcomipc.c:829:12: error: call to undeclared function 'FIELD_PREP'; 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:
[andersson@kernel.org andrew@lunn.ch ath10k@lists.infradead.org axboe@kernel.dk brgl@kernel.org conor@kernel.org davem@davemloft.net devicetree@vger.kernel.org devnull@kernel.org edumazet@google.com george.moussalem@outlook.com hkallweit1@gmail.com horms@kernel.org jjohnson@kernel.org johannes@sipsolutions.net konradybcio@kernel.org krzk@kernel.org kuba@kernel.org linux-arm-msm@vger.kernel.org linux-block@vger.kernel.org linux-bluetooth@vger.kernel.org linux-kernel@vger.kernel.org linux-mmc@vger.kernel.org linux-remoteproc@vger.kernel.org linux-wireless@vger.kernel.org linux@armlinux.org.uk luiz.dentz@gmail.com marcel@holtmann.org mathieu.poirier@linaro.org netdev@vger.kernel.org p.zabel@pengutronix.de pabeni@redhat.com quic_bgodavar@quicinc.com quic_rjliao@quicinc.com robh@kernel.org saravanak@kernel.org ulfh@kernel.org]

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-06-29 14:46 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=6a428537.854d4ab9.360e1d.0009.GAE@google.com \
    --to=syzbot+ci65ba89adbec7a7b3@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.