[moderation/CI] Re: PCI: liveupdate: PCI core support for Live Update

[syzbot ci]

syzbot ci has tested the following series

[v5] PCI: liveupdate: PCI core support for Live Update
https://lore.kernel.org/all/20260512184846.1...@google.com
* [PATCH v5 01/11] PCI: liveupdate: Set up FLB handler for the PCI core
* [PATCH v5 02/11] PCI: liveupdate: Track outgoing preserved PCI devices
* [PATCH v5 03/11] PCI: liveupdate: Track incoming preserved PCI devices
* [PATCH v5 04/11] PCI: liveupdate: Document driver binding responsibilities
* [PATCH v5 05/11] PCI: liveupdate: Keep bus numbers constant during Live Update
* [PATCH v5 06/11] PCI: liveupdate: Auto-preserve upstream bridges across Live Update
* [PATCH v5 07/11] PCI: liveupdate: Inherit ACS flags in incoming preserved devices
* [PATCH v5 08/11] PCI: liveupdate: Inherit ARI Forwarding Enable on preserved bridges
* [PATCH v5 09/11] PCI: liveupdate: Freeze preservation status during shutdown
* [PATCH v5 10/11] PCI: liveupdate: Do not disable bus mastering on preserved devices during kexec
* [PATCH v5 11/11] Documentation: PCI: Add documentation for Live Update

and found the following issue:
kernel build error

Full report is available here:
https://ci.syzbot.org/series/2bd36b56-6749-4b60-8011-0dc81da9bbbe

***

kernel build error

tree: linux-next
URL: https://kernel.googlesource.com/pub/scm/linux/kernel/git/next/linux-next
base: 34e8f02817e31826e76bb2ded48bf28fe921f20b
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/0fc4ac39-5a07-470f-8057-4c357e165522/config

drivers/pci/liveupdate.h:38: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: syz...@syzkaller.appspotmail.com

---
This report is generated by a bot. It may contain errors.
syzbot ci engineers can be reached at syzk...@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:
[ajayac...@nvidia.com al...@shazbot.org bhel...@google.com chr...@kernel.org cor...@lwn.net dmat...@google.com gr...@amazon.com jaco...@linux.microsoft.com j...@nvidia.com jrh...@google.com ke...@lists.infradead.org leo...@nvidia.com linu...@vger.kernel.org linux-...@vger.kernel.org linu...@kvack.org linu...@vger.kernel.org lu...@wunner.de pa...@nvidia.com pasha.t...@soleen.com pr...@google.com prat...@kernel.org rien...@google.com rp...@kernel.org sae...@nvidia.com sk...@linuxfoundation.org skha...@google.com vip...@google.com wi...@nvidia.com yi.l...@intel.com]

If the report looks fine to you, reply with:
#syz upstream

If the report is a false positive, reply with
#syz invalid