From: syzbot <syzbot+0cd0fb4cf3f4722d6663@syzkaller.appspotmail.com>
To: contact@henrialfonso.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [usb?] WARNING in dib0700_ctrl_rd/usb_submit_urb
Date: Sun, 21 Jun 2026 02:57:02 -0700 [thread overview]
Message-ID: <6a37b56e.1841f4b3.127ecf.0006.GAE@google.com> (raw)
In-Reply-To: <19ee8abaab6.247682c01322736.5993741758980597841@henrialfonso.com>
Hello,
syzbot tried to test the proposed patch but the build/boot failed:
failed to apply patch:
error: No valid patches in input (allow with "--allow-empty")
Tested on:
commit: 9afe6529 Merge tag 'x86_urgent_for_6.16-rc3' of git://..
git tree: git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
kernel config: https://syzkaller.appspot.com/x/.config?x=59da38148f3a3d24
dashboard link: https://syzkaller.appspot.com/bug?extid=0cd0fb4cf3f4722d6663
compiler:
patch: https://syzkaller.appspot.com/x/patch.diff?x=17f49ff2580000
next parent reply other threads:[~2026-06-21 9:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <19ee8abaab6.247682c01322736.5993741758980597841@henrialfonso.com>
2026-06-21 9:57 ` syzbot [this message]
[not found] <19eeb185b07.1092251c1402089.3645881485633059809@henrialfonso.com>
2026-06-21 17:42 ` [syzbot] [usb?] WARNING in dib0700_ctrl_rd/usb_submit_urb syzbot
[not found] <19eeadee149.6b36a0681396909.4018084711379907981@henrialfonso.com>
2026-06-21 16:45 ` syzbot
[not found] <19eeacf9be8.2dfdb8611395446.235320573208400958@henrialfonso.com>
2026-06-21 15:42 ` syzbot
[not found] <19eea77c618.dada2211385513.4507326562881481209@henrialfonso.com>
2026-06-21 15:06 ` syzbot
[not found] <19eea71f424.3cd15d531384711.2172053588253764796@henrialfonso.com>
2026-06-21 13:50 ` syzbot
2025-06-20 3:04 syzbot
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=6a37b56e.1841f4b3.127ecf.0006.GAE@google.com \
--to=syzbot+0cd0fb4cf3f4722d6663@syzkaller.appspotmail.com \
--cc=contact@henrialfonso.com \
--cc=linux-kernel@vger.kernel.org \
--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.