Archive-only list for syzbot
 help / color / mirror / Atom feed
From: syzbot ci <syzbot+ciac9eee7ac2b7e416@syzkaller.appspotmail.com>
To: syzkaller-upstream-moderation@googlegroups.com
Cc: syzbot@lists.linux.dev
Subject: [moderation/CI] Re: net: pcs: Introduce support for fwnode PCS
Date: Mon, 15 Jun 2026 08:35:04 -0700	[thread overview]
Message-ID: <6a301ba8.428ffe26.258b27.016d.GAE@google.com> (raw)

syzbot ci has tested the following series

[v7] net: pcs: Introduce support for fwnode PCS
https://lore.kernel.org/all/20260615122950.22281-1-ansuelsmth@gmail.com
* [PATCH net-next v7 01/12] net: phylink: keep and use MAC supported_interfaces in phylink struct
* [PATCH net-next v7 02/12] net: phylink: introduce internal phylink PCS handling
* [PATCH net-next v7 03/12] net: phylink: add phylink_release_pcs() to externally release a PCS
* [PATCH net-next v7 04/12] net: pcs: implement Firmware node support for PCS driver
* [PATCH net-next v7 05/12] net: phylink: support late PCS provider attach
* [PATCH net-next v7 06/12] net: Document PCS subsystem
* [PATCH net-next v7 07/12] MAINTAINERS: add myself as PCS subsystem maintainer
* [PATCH net-next v7 08/12] of: property: fw_devlink: Add support for "pcs-handle"
* [PATCH net-next v7 09/12] net: phylink: add .pcs_link_down PCS OP
* [PATCH net-next v7 10/12] dt-bindings: net: pcs: Document support for Airoha Ethernet PCS
* [PATCH net-next v7 11/12] net: pcs: airoha: add PCS driver for Airoha AN7581 SoC
* [PATCH net-next v7 12/12] net: airoha: add phylink support

and found the following issue:
kernel build error

Full report is available here:
https://ci.syzbot.org/series/8697e3f4-ead4-4d5d-9068-ed8aecbd0b54

***

kernel build error

tree:      net-next
URL:       https://kernel.googlesource.com/pub/scm/linux/kernel/git/netdev/net-next.git
base:      2319688890d97c63da423a3c57c23b4ab5952dfc
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/519594d7-0c1e-4dad-9a21-226aa905fdec/config

drivers/net/phy/phylink.c:2218:3: error: call to undeclared function 'unregister_fwnode_pcs_notifier'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]

***

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 patch for this bug, please reply with `#syz test`
(should be on a separate line).

The patch should be attached to the email.
Note: arguments like custom git repos and branches are not supported.

The email will later be sent to:
[andrew@lunn.ch ansuelsmth@gmail.com conor@kernel.org corbet@lwn.net daniel@makrotopia.org davem@davemloft.net devicetree@vger.kernel.org edumazet@google.com hkallweit1@gmail.com horms@kernel.org justinstitt@google.com krzk@kernel.org kuba@kernel.org linux-arm-kernel@lists.infradead.org linux-doc@vger.kernel.org linux-kernel@vger.kernel.org linux-mediatek@lists.infradead.org linux@armlinux.org.uk llvm@lists.linux.dev lorenzo@kernel.org morbo@google.com nathan@kernel.org netdev@vger.kernel.org nick.desaulniers@gmail.com p.zabel@pengutronix.de pabeni@redhat.com robh@kernel.org saravanak@kernel.org skhan@linuxfoundation.org]

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-06-15 15:35 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=6a301ba8.428ffe26.258b27.016d.GAE@google.com \
    --to=syzbot+ciac9eee7ac2b7e416@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