From: syzbot ci <syzbot+ci68b7621f6fabdcd1@syzkaller.appspotmail.com>
To: syzkaller-upstream-moderation@googlegroups.com
Cc: syzbot@lists.linux.dev
Subject: [moderation/CI] Re: dpll: Core improvements and ice E825-C SyncE support
Date: Mon, 02 Feb 2026 11:50:28 -0800 [thread overview]
Message-ID: <69810004.050a0220.1d0a41.002c.GAE@google.com> (raw)
syzbot ci has tested the following series
[v4] dpll: Core improvements and ice E825-C SyncE support
https://lore.kernel.org/all/20260202171638.17427-1-ivecera@redhat.com
* [PATCH net-next v4 1/9] dpll: Allow associating dpll pin with a firmware node
* [PATCH net-next v4 2/9] dpll: zl3073x: Associate pin with fwnode handle
* [PATCH net-next v4 3/9] dpll: Add notifier chain for dpll events
* [PATCH net-next v4 4/9] dpll: Support dynamic pin index allocation
* [PATCH net-next v4 5/9] dpll: zl3073x: Add support for mux pin type
* [PATCH net-next v4 6/9] dpll: Enhance and consolidate reference counting logic
* [PATCH net-next v4 7/9] dpll: Add reference count tracking support
* [PATCH net-next v4 8/9] drivers: Add support for DPLL reference count tracking
* [PATCH net-next v4 9/9] ice: dpll: Support E825-C SyncE and dynamic pin discovery
and found the following issue:
kernel build error
Full report is available here:
https://ci.syzbot.org/series/6e56fe77-3149-48fd-a446-971924fed7c5
***
kernel build error
tree: net-next
URL: https://kernel.googlesource.com/pub/scm/linux/kernel/git/netdev/net-next.git
base: a22f57757f7e88c890499265c383ecb32900b645
arch: amd64
compiler: Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8
config: https://ci.syzbot.org/builds/067661f9-73a6-46e9-bc30-e091796a524d/config
./include/linux/dpll.h:235:1: error: expected identifier or '('
***
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:
[aleksander.lobakin@intel.com aleksandr.loktionov@intel.com andrew@lunn.ch anthony.l.nguyen@intel.com arkadiusz.kubalewski@intel.com davem@davemloft.net edumazet@google.com grzegorz.nitka@intel.com intel-wired-lan@lists.osuosl.org ivecera@redhat.com jiri@resnulli.us jonathan.lemon@gmail.com kuba@kernel.org leon@kernel.org linux-kernel@vger.kernel.org linux-rdma@vger.kernel.org mbloch@nvidia.com netdev@vger.kernel.org pabeni@redhat.com poros@redhat.com prathosh.satish@microchip.com przemyslaw.kitszel@intel.com richardcochran@gmail.com saeedm@nvidia.com tariqt@nvidia.com vadim.fedorenko@linux.dev]
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-02-02 19:50 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=69810004.050a0220.1d0a41.002c.GAE@google.com \
--to=syzbot+ci68b7621f6fabdcd1@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