From: syzbot ci <syzbot+ci5b8d854ef820d7f9@syzkaller.appspotmail.com>
To: syzkaller-upstream-moderation@googlegroups.com
Cc: syzbot@lists.linux.dev
Subject: [moderation/CI] Re: ax88179_178a: Add support for AX88179A-based chips
Date: Thu, 03 Sep 2026 07:10:08 -0700 [thread overview]
Message-ID: <6a997fc0.9266084e.bf0d7.025b.GAE@google.com> (raw)
syzbot ci has tested the following series
[v9] ax88179_178a: Add support for AX88179A-based chips
https://lore.kernel.org/all/20260902-ax88179a-v9-0-8e6d7710a2ae@birger-koblitz.de
* [PATCH net-next v9 01/15] phylink: Add phylink_mac_interrupt
* [PATCH net-next v9 02/15] phylib: Add support for PHYs with broken forced mode
* [PATCH net-next v9 03/15] ax88179_178a: Fix endianness of pause watermark register
* [PATCH net-next v9 04/15] ax88179_178a: Split driver into library and device specific code
* [PATCH net-next v9 05/15] ax88179_178a: Add netdev2data() convenience function
* [PATCH net-next v9 06/15] ax88179_178a: Add HW support for AX179A-based chips
* [PATCH net-next v9 07/15] ax88179_178a: Add EEE configuration support for AX88179A MACs
* [PATCH net-next v9 08/15] ax88179_178a: Add EEE configuration support for AX88179A PHYs
* [PATCH net-next v9 09/15] ax88179_178a: Add VLAN offload support for AX88179A
* [PATCH net-next v9 10/15] ax88179_178a: Add AX179A/AX279 multicast configuration
* [PATCH net-next v9 11/15] ax88179_178a: Add Suspend/resume support for AX88179A/772D/279
* [PATCH net-next v9 12/15] ax88179_178a: Add ethtool get_drvinfo
* [PATCH net-next v9 13/15] ax88179_178a: Update driver name and information
* [PATCH net-next v9 14/15] ax88179_178a: Add support for AX88179A/772D/279 EEPROM access
* [PATCH net-next v9 15/15] ax88796b: Add support for AX88772D, AX88179A and AX88279
and found the following issue:
kernel build error
Full report is available here:
https://ci.syzbot.org/series/da1ee2ab-0378-4af7-9df2-20c15b1df325
***
kernel build error
tree: linux-next
URL: https://kernel.googlesource.com/pub/scm/linux/kernel/git/next/linux-next
base: 1bb784eb6e38fd73143f021608e4ef3095d0c0d7
arch: amd64
compiler: Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8
config: https://ci.syzbot.org/builds/a18e865e-94ef-47f0-8f08-230ab0bd7bb1/config
drivers/net/usb/ax88179a_devices.c:123:24: error: use of undeclared identifier 'data'; did you mean '_data'?
drivers/net/usb/ax88179a_devices.c:123:28: error: member reference base type 'char' is not a structure or union
***
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 fix for this bug, please reply with `#syz test`
(on a separate line) and attach the patch to the email.
Notes:
- The patch will be applied on top of the tested series (as an
incremental fix).
- To test a new version of the whole series, please send it directly
to syzbot@lists.linux.dev.
- Arguments like custom git repos and branches are not supported.
The email will later be sent to:
[andrew@lunn.ch davem@davemloft.net edumazet@google.com hkallweit1@gmail.com kuba@kernel.org linux-kernel@vger.kernel.org linux-usb@vger.kernel.org linux@armlinux.org.uk mail@birger-koblitz.de netdev@vger.kernel.org neuromoments@gmail.com pabeni@redhat.com]
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-09-03 14:10 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=6a997fc0.9266084e.bf0d7.025b.GAE@google.com \
--to=syzbot+ci5b8d854ef820d7f9@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