[moderation/CI] Re: ACPI: Add support for ACPI RAS2 feature table

[syzbot ci]

syzbot ci has tested the following series

[v22] ACPI: Add support for ACPI RAS2 feature table
https://lore.kernel.org/all/20260709210750.424...@gmail.com
* [PATCH v22 1/2] ACPI:RAS2: Add driver for the ACPI RAS2 feature table
* [PATCH v22 2/2] ras: mem: Add ACPI RAS2 memory driver

and found the following issue:
kernel build error

Full report is available here:
https://ci.syzbot.org/series/5040b478-7bdb-4326-a6b4-5685754ec2d4

***

kernel build error

tree: mm-new
URL: https://kernel.googlesource.com/pub/scm/linux/kernel/git/akpm/mm.git
base: 1e692e85500fd3a971da0241f044f4572b2be8b6
arch: amd64
compiler: Debian clang version 22.1.6 (++20260514074242+fc4aad7b5db3-1~exp1~20260514074407.73), Debian LLD 22.1.6
config: https://ci.syzbot.org/builds/4aba36a3-6777-42f1-bcad-f10d6ceb7cdf/config

drivers/ras/acpi_ras2.c:68:2: error: call to undeclared function 'iowrite64'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
drivers/ras/acpi_ras2.c:92:20: error: call to undeclared function 'ioread64'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
drivers/ras/acpi_ras2.c:115:2: error: call to undeclared function 'iowrite64'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
drivers/ras/acpi_ras2.c:339:3: error: call to undeclared function 'iowrite64'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
drivers/ras/acpi_ras2.c:447:2: error: call to undeclared function 'iowrite64'; 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: 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:
[ak...@linux-foundation.org asho...@oss.qualcomm.com b...@alien8.de dave....@linux.intel.com dfer...@amperecomputing.com due...@google.com erdem...@google.com gth...@google.com james...@arm.com jiaq...@google.com ji...@kernel.org jon....@amd.com jthou...@google.com kangka...@futurewei.com le...@kernel.org linux...@vger.kernel.org linu...@vger.kernel.org linux...@vger.kernel.org linu...@kvack.org linu...@huawei.com mch...@kernel.org naoya.h...@nec.com nifa...@gmail.com pgo...@google.com prime...@hisilicon.com raf...@kernel.org rien...@google.com robert...@huawei.com rp...@kernel.org shijuj...@gmail.com somasun...@hpe.com tanxi...@huawei.com tony...@intel.com wanghu...@huawei.com w...@os.amperecomputing.com wsch...@amperecomputing.com yazen....@amd.com]

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

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