From: syzbot ci <syzbot+cicc6ab7b4d8f508c1@syzkaller.appspotmail.com>
To: syzkaller-upstream-moderation@googlegroups.com
Cc: syzbot@lists.linux.dev
Subject: [moderation/CI] Re: Bluetooth: hci_sync: Initial LE Channel Sounding support by defining required HCI command/event structures.
Date: Tue, 16 Dec 2025 05:47:50 -0800 [thread overview]
Message-ID: <69416306.a70a0220.33cd7b.013f.GAE@google.com> (raw)
syzbot ci has tested the following series
[v1] Bluetooth: hci_sync: Initial LE Channel Sounding support by defining required HCI command/event structures.
https://lore.kernel.org/all/20251216113753.3969183-1-naga.akella@oss.qualcomm.com
* [PATCH v1] Bluetooth: hci_sync: Initial LE Channel Sounding support by defining required HCI command/event structures.
and found the following issue:
kernel build error
Full report is available here:
https://ci.syzbot.org/series/a48bd25e-42b6-4a0c-bddb-26e955f3e39e
***
kernel build error
tree: net-next
URL: https://kernel.googlesource.com/pub/scm/linux/kernel/git/netdev/net-next.git
base: 8f7aa3d3c7323f4ca2768a9e74ebbe359c4f8f88
arch: amd64
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
config: https://ci.syzbot.org/builds/afe547a4-e1e3-444b-89cc-794f55470c1d/config
./include/net/bluetooth/hci.h:2430:8: error: redefinition of 'hci_cp_le_cs_set_proc_param'
***
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:
[anubhavg@qti.qualcomm.com davem@davemloft.net edumazet@google.com hbandi@qti.qualcomm.com horms@kernel.org johan.hedberg@gmail.com kuba@kernel.org linux-bluetooth@vger.kernel.org linux-kernel@vger.kernel.org luiz.dentz@gmail.com marcel@holtmann.org mohamull@qti.qualcomm.com naga.akella@oss.qualcomm.com netdev@vger.kernel.org pabeni@redhat.com]
If the report looks fine to you, reply with:
#syz upstream
reply other threads:[~2025-12-16 13:47 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=69416306.a70a0220.33cd7b.013f.GAE@google.com \
--to=syzbot+cicc6ab7b4d8f508c1@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