From: syzbot <syzbot+96c36598b73a9d3f3e25@syzkaller.appspotmail.com>
To: linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-next@vger.kernel.org, luiz.dentz@gmail.com,
marcel@holtmann.org, sfr@canb.auug.org.au,
syzkaller-bugs@googlegroups.com
Subject: [syzbot] linux-next build error (17)
Date: Thu, 11 Jul 2024 02:05:23 -0700 [thread overview]
Message-ID: <000000000000236b8d061cf510dc@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: f477dd6eede3 Add linux-next specific files for 20240711
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=1634d47e980000
kernel config: https://syzkaller.appspot.com/x/.config?x=98dd8c4bab5cdce
dashboard link: https://syzkaller.appspot.com/bug?extid=96c36598b73a9d3f3e25
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+96c36598b73a9d3f3e25@syzkaller.appspotmail.com
drivers/bluetooth/hci_qca.c:2501:10: error: label at end of compound statement: expected statement
---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzkaller@googlegroups.com.
syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title
If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)
If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report
If you want to undo deduplication, reply with:
#syz undup
reply other threads:[~2024-07-11 9:05 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=000000000000236b8d061cf510dc@google.com \
--to=syzbot+96c36598b73a9d3f3e25@syzkaller.appspotmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=sfr@canb.auug.org.au \
--cc=syzkaller-bugs@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.