From: syzbot <syzbot+13f8286fa2de04a7cd48@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com,
xiaopei01@kylinos.cn, xiaopeitux@foxmail.com
Subject: Re: [syzbot] [input?] [usb?] WARNING in asus_remove
Date: Thu, 29 Jan 2026 23:41:02 -0800 [thread overview]
Message-ID: <697c608e.a70a0220.9914.002c.GAE@google.com> (raw)
In-Reply-To: <tencent_42595E6527E47355AEFA116CDCF2543C9008@qq.com>
Hello,
syzbot tried to test the proposed patch but the build/boot failed:
drivers/hid/hid-asus.c:364:6: error: use of undeclared identifier 'drvdata'
drivers/hid/hid-asus.c:366:3: error: use of undeclared identifier 'drvdata'
drivers/hid/hid-asus.c:366:23: error: use of undeclared identifier 'drvdata'
drivers/hid/hid-asus.c:367:18: error: use of undeclared identifier 'drvdata'
Tested on:
commit: 33a647c6 Add linux-next specific files for 20260129
git tree: linux-next
kernel config: https://syzkaller.appspot.com/x/.config?x=750532df2c47a03
dashboard link: https://syzkaller.appspot.com/bug?extid=13f8286fa2de04a7cd48
compiler: Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8
patch: https://syzkaller.appspot.com/x/patch.diff?x=12d1a45a580000
next prev parent reply other threads:[~2026-01-30 7:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-29 18:44 [syzbot] [input?] [usb?] WARNING in asus_remove syzbot
2026-01-30 6:24 ` Sahil Chandna
2026-01-30 7:04 ` syzbot
2026-02-02 20:28 ` Jiri Kosina
2026-02-02 20:47 ` Jiri Kosina
2026-01-30 7:21 ` [PATCH] test: hid_asus xiaopeitux
2026-01-30 7:41 ` syzbot [this message]
2026-01-30 7:50 ` xiaopeitux
2026-01-30 8:10 ` [syzbot] [input?] [usb?] WARNING in asus_remove syzbot
2026-01-30 9:14 ` Hillf Danton
2026-01-30 9:38 ` syzbot
2026-02-03 10:09 ` Sahil Chandna
2026-02-03 13:35 ` 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=697c608e.a70a0220.9914.002c.GAE@google.com \
--to=syzbot+13f8286fa2de04a7cd48@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=xiaopei01@kylinos.cn \
--cc=xiaopeitux@foxmail.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.