* linux-next: Tree for Jun 26
From: Mark Brown @ 2026-06-29 11:21 UTC (permalink / raw)
To: Linux Next Mailing List; +Cc: Linux Kernel Mailing List
[-- Attachment #1: Type: text/plain, Size: 1737 bytes --]
Hi all,
The merge window is open, so please to not addd any v7.2 material
to your linux-next included branches until after the merge window closes.
Changes since 20260625:
None.
Non-merge commits (relative to Linus' tree): 1105
1119 files changed, 52070 insertions(+), 22217 deletions(-)
----------------------------------------------------------------------------
I have created today's linux-next tree at
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
(patches at https://www.kernel.org/pub/linux/kernel/next/ ). If you
are tracking the linux-next tree using git, you should not use "git pull"
to do so as that will try to merge the new linux-next release with the
old one. You should use "git fetch" and checkout or reset to the new
master.
You can see which trees have been included by looking in the Next/Trees
file in the source. There is also the merge.log file in the Next
directory. Between each merge, the tree was built with a defconfig
for arm64, an allmodconfig for x86_64, a multi_v7_defconfig for arm,
an arm64 build of various kselftests, a KUnit build and run on arm64,
and a native build of tools/perf. After the final fixups (if any), I do
an x86_64 modules_install followed by builds for x86_64 allnoconfig,
arm64 allyesconfig, powerpc allnoconfig (32 and 64 bit),
ppc44x_defconfig and pseries_le_defconfig and i386, s390, sparc and
sparc64 defconfig and htmldocs.
Below is a summary of the state of the merge.
I am currently merging 425 trees (counting Linus' and 131 trees of bug
fix patches pending for the current release).
Stats about the size of the tree over time can be seen at
http://neuling.org/linux-next-size.html .
Thanks to Paul Gortmaker for triage and bug fixes.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
^ permalink raw reply
* Re: [regression] synaptics-rmi4: Failed to read the Control Register Descriptor: EIO
From: Dmitry Torokhov @ 2026-06-28 5:43 UTC (permalink / raw)
To: David Heidelberg; +Cc: linux-input, Linux Next Mailing List
In-Reply-To: <916192e4-7d2c-4463-8576-3cfe9e36faa2@ixit.cz>
On Sat, Jun 27, 2026 at 12:06:29PM +0200, David Heidelberg wrote:
> On 26/06/2026 23:18, Dmitry Torokhov wrote:
> > Hi David,
> >
> > On Fri, Jun 26, 2026 at 11:09:54PM +0200, David Heidelberg wrote:
> > > With next-20260626 without any additional patches, the synaptics fails on
> > > OnePlus 6T with:
> > >
> > > ```
> > > [ 16.620292] rmi4_i2c 12-0020: registering I2C-connected sensor
> > > [ 16.857617] rmi4_f01 rmi4-00.fn01: found RMI device, manufacturer:
> > > Synaptics, product: S3706B, fw id: 2852315
> > > [ 16.867324] rmi4_f12 rmi4-00.fn12: Failed to read the Control Register
> > > Descriptor: -5
> > > [ 16.867338] rmi4_f12 rmi4-00.fn12: probe with driver rmi4_f12 failed with
> > > error -5
> > > ```
> >
> > Yes, at least a98518e72439 "Input: rmi4 - fix register descriptor address
> > calculation" is wrong and needs to be reverted.
>
> That did it for me, now the TS works again.
Thank you for letting me know.
--
Dmitry
^ permalink raw reply
* Re: [regression] synaptics-rmi4: Failed to read the Control Register Descriptor: EIO
From: David Heidelberg @ 2026-06-27 10:06 UTC (permalink / raw)
To: Dmitry Torokhov; +Cc: linux-input, Linux Next Mailing List
In-Reply-To: <aj7saJXgFX--gP_8@google.com>
On 26/06/2026 23:18, Dmitry Torokhov wrote:
> Hi David,
>
> On Fri, Jun 26, 2026 at 11:09:54PM +0200, David Heidelberg wrote:
>> With next-20260626 without any additional patches, the synaptics fails on
>> OnePlus 6T with:
>>
>> ```
>> [ 16.620292] rmi4_i2c 12-0020: registering I2C-connected sensor
>> [ 16.857617] rmi4_f01 rmi4-00.fn01: found RMI device, manufacturer:
>> Synaptics, product: S3706B, fw id: 2852315
>> [ 16.867324] rmi4_f12 rmi4-00.fn12: Failed to read the Control Register
>> Descriptor: -5
>> [ 16.867338] rmi4_f12 rmi4-00.fn12: probe with driver rmi4_f12 failed with
>> error -5
>> ```
>
> Yes, at least a98518e72439 "Input: rmi4 - fix register descriptor address
> calculation" is wrong and needs to be reverted.
That did it for me, now the TS works again.
Thank you
David
^ permalink raw reply
* [STATUS] next/master - 3d5670d672ae08b8c534b7beed6f57c8b44e7b43
From: KernelCI bot @ 2026-06-27 2:30 UTC (permalink / raw)
To: kernelci-results; +Cc: linux-next
Hello,
Status summary for next/master
Dashboard:
https://d.kernelci.org/c/next/master/3d5670d672ae08b8c534b7beed6f57c8b44e7b43/
giturl: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
branch: master
commit hash: 3d5670d672ae08b8c534b7beed6f57c8b44e7b43
origin: maestro
test start time: 2026-06-26 14:47:34.599000+00:00
Builds: 66 ✅ 2 ❌ 0 ⚠️
Boots: 169 ✅ 4 ❌ 0 ⚠️
Tests: 31254 ✅ 5370 ❌ 7026 ⚠️
### POSSIBLE REGRESSIONS
No possible regressions observed.
### FIXED REGRESSIONS
Hardware: bcm2711-rpi-4-b
> Config: defconfig+lab-setup+kselftest
- Architecture/compiler: arm64/gcc-14
- kselftest.dt
last run: https://d.kernelci.org/test/maestro:6a3e9bd36de4dcc0f449375e
history: > ❌ > ❌ > ✅ > ✅
- kselftest.dt.dt_test_unprobed_devices_sh
last run: https://d.kernelci.org/test/maestro:6a3e9c646de4dcc0f4493ae1
history: > ❌ > ❌ > ✅ > ✅
- kselftest.dt.dt_test_unprobed_devices_sh_gpu
last run: https://d.kernelci.org/test/maestro:6a3e9c646de4dcc0f4493b18
history: > ❌ > ❌ > ✅ > ✅
Hardware: bcm2837-rpi-3-b-plus
> Config: defconfig+lab-setup+kselftest
- Architecture/compiler: arm64/gcc-14
- kselftest.device_error_logs
last run: https://d.kernelci.org/test/maestro:6a3e9bb96de4dcc0f4493679
history: > ❌ > ✅
- kselftest.device_error_logs.devices_error_logs_test_device_error_logs_py
last run: https://d.kernelci.org/test/maestro:6a3e9e316de4dcc0f44987c8
history: > ❌ > ✅
- kselftest.dt.dt_test_unprobed_devices_sh_gpu
last run: https://d.kernelci.org/test/maestro:6a3e9fb06de4dcc0f4499b55
history: > ❌ > ✅
Hardware: mt8195-cherry-tomato-r2
> Config: defconfig+lab-setup+arm64-chromebook+CONFIG_MODULE_COMPRESS=n+CONFIG_MODULE_COMPRESS_NONE=y
- Architecture/compiler: arm64/gcc-14
- kselftest.dt.dt_test_unprobed_devices_sh_mt8195-sound
last run: https://d.kernelci.org/test/maestro:6a3e9a866de4dcc0f449056d
history: > ❌ > ✅ > ✅
- kselftest.dt.dt_test_unprobed_devices_sh_soc_dma-controller_1c104000
last run: https://d.kernelci.org/test/maestro:6a3e9a866de4dcc0f4490502
history: > ❌ > ✅ > ✅
- kselftest.dt.dt_test_unprobed_devices_sh_soc_dma-controller_1c105000
last run: https://d.kernelci.org/test/maestro:6a3e9a866de4dcc0f4490501
history: > ❌ > ✅ > ✅
- kselftest.dt.dt_test_unprobed_devices_sh_soc_dma-controller_1c106000
last run: https://d.kernelci.org/test/maestro:6a3e9a866de4dcc0f4490500
history: > ❌ > ✅ > ✅
- kselftest.dt.dt_test_unprobed_devices_sh_soc_dma-controller_1c107000
last run: https://d.kernelci.org/test/maestro:6a3e9a866de4dcc0f44904ff
history: > ❌ > ✅ > ✅
- kselftest.dt.dt_test_unprobed_devices_sh_soc_dma-controller_1c108000
last run: https://d.kernelci.org/test/maestro:6a3e9a866de4dcc0f44904fe
history: > ❌ > ✅ > ✅
- kselftest.dt.dt_test_unprobed_devices_sh_soc_dma-controller_1c109000
last run: https://d.kernelci.org/test/maestro:6a3e9a866de4dcc0f44904fd
history: > ❌ > ✅ > ✅
- kselftest.dt.dt_test_unprobed_devices_sh_soc_dma-controller_1c10a000
last run: https://d.kernelci.org/test/maestro:6a3e9a866de4dcc0f44904fc
history: > ❌ > ✅ > ✅
- kselftest.dt.dt_test_unprobed_devices_sh_soc_dma-controller_1c10b000
last run: https://d.kernelci.org/test/maestro:6a3e9a866de4dcc0f44904fb
history: > ❌ > ✅ > ✅
- kselftest.dt.dt_test_unprobed_devices_sh_soc_dp-intf_1c015000
last run: https://d.kernelci.org/test/maestro:6a3e9a866de4dcc0f44904fa
history: > ❌ > ✅ > ✅
- kselftest.dt.dt_test_unprobed_devices_sh_soc_dp-intf_1c113000
last run: https://d.kernelci.org/test/maestro:6a3e9a866de4dcc0f44904f9
history: > ❌ > ✅ > ✅
- kselftest.dt.dt_test_unprobed_devices_sh_soc_hdr-engine_1c114000
last run: https://d.kernelci.org/test/maestro:6a3e9a866de4dcc0f44904f0
history: > ❌ > ✅ > ✅
- kselftest.dt.dt_test_unprobed_devices_sh_soc_jpeg-decoder_1a040000
last run: https://d.kernelci.org/test/maestro:6a3e9a866de4dcc0f44904df
history: > ❌ > ✅ > ✅
- kselftest.dt.dt_test_unprobed_devices_sh_soc_jpeg-decoder_1a040000_jpgdec_0_0
last run: https://d.kernelci.org/test/maestro:6a3e9a866de4dcc0f44904de
history: > ❌ > ✅ > ✅
- kselftest.dt.dt_test_unprobed_devices_sh_soc_jpeg-decoder_1a040000_jpgdec_0_10000
last run: https://d.kernelci.org/test/maestro:6a3e9a866de4dcc0f44904dd
history: > ❌ > ✅ > ✅
- kselftest.dt.dt_test_unprobed_devices_sh_soc_jpeg-decoder_1a040000_jpgdec_1_0
last run: https://d.kernelci.org/test/maestro:6a3e9a866de4dcc0f44904dc
history: > ❌ > ✅ > ✅
- kselftest.dt.dt_test_unprobed_devices_sh_soc_jpeg-encoder_1a030000
last run: https://d.kernelci.org/test/maestro:6a3e9a866de4dcc0f44904db
history: > ❌ > ✅ > ✅
- kselftest.dt.dt_test_unprobed_devices_sh_soc_jpeg-encoder_1a030000_jpgenc_0_0
last run: https://d.kernelci.org/test/maestro:6a3e9a866de4dcc0f44904da
history: > ❌ > ✅ > ✅
- kselftest.dt.dt_test_unprobed_devices_sh_soc_jpeg-encoder_1a030000_jpgenc_1_0
last run: https://d.kernelci.org/test/maestro:6a3e9a866de4dcc0f44904d9
history: > ❌ > ✅ > ✅
- kselftest.dt.dt_test_unprobed_devices_sh_soc_ovl_1c000000
last run: https://d.kernelci.org/test/maestro:6a3e9a866de4dcc0f44904b0
history: > ❌ > ✅ > ✅
- kselftest.dt.dt_test_unprobed_devices_sh_soc_rdma_1c002000
last run: https://d.kernelci.org/test/maestro:6a3e9a866de4dcc0f44904a5
history: > ❌ > ✅ > ✅
- kselftest.dt.dt_test_unprobed_devices_sh_soc_video-codec_18000000
last run: https://d.kernelci.org/test/maestro:6a3e9a866de4dcc0f4490471
history: > ❌ > ✅ > ✅
- kselftest.dt.dt_test_unprobed_devices_sh_soc_video-codec_18000000_video-codec_10000
last run: https://d.kernelci.org/test/maestro:6a3e9a866de4dcc0f4490470
history: > ❌ > ✅ > ✅
- kselftest.dt.dt_test_unprobed_devices_sh_soc_video-codec_18000000_video-codec_2000
last run: https://d.kernelci.org/test/maestro:6a3e9a866de4dcc0f449046f
history: > ❌ > ✅ > ✅
- kselftest.dt.dt_test_unprobed_devices_sh_soc_video-codec_18000000_video-codec_25000
last run: https://d.kernelci.org/test/maestro:6a3e9a866de4dcc0f449046e
history: > ❌ > ✅ > ✅
- kselftest.dt.dt_test_unprobed_devices_sh_soc_video-codec_1a020000
last run: https://d.kernelci.org/test/maestro:6a3e9a866de4dcc0f449046d
history: > ❌ > ✅ > ✅
### UNSTABLE TESTS
Hardware: glymur-crd
> Config: defconfig+lab-setup+kselftest
- Architecture/compiler: arm64/gcc-14
- kselftest.dt.dt_test_unprobed_devices_sh_soc_0_pci_1c00000
last run: https://d.kernelci.org/test/maestro:6a3ea83f6de4dcc0f44a2d19
history: > ✅ > ❌ > ✅
Hardware: qcs6490-rb3gen2
> Config: defconfig+lab-setup+kselftest
- Architecture/compiler: arm64/gcc-14
- kselftest.breakpoints
last run: https://d.kernelci.org/test/maestro:6a3e9b646de4dcc0f449322b
history: > ❌ > ❌ > ✅ > ❌ > ❌
Hardware: qcs8300-ride
> Config: defconfig+lab-setup+kselftest
- Architecture/compiler: arm64/gcc-14
- kselftest.coredump
last run: https://d.kernelci.org/test/maestro:6a3e9b8b6de4dcc0f44933c2
history: > ❌ > ❌ > ✅ > ❌ > ❌
- kselftest.dt.dt_test_unprobed_devices_sh_soc_0_ethernet_23040000_mdio_phy_8
last run: https://d.kernelci.org/test/maestro:6a3ea4dd6de4dcc0f449e516
history: > ✅ > ⚠️ > ✅
- kselftest.dt.dt_test_unprobed_devices_sh_soc_0_pci_1c00000_pcie_0_wifi_0
last run: https://d.kernelci.org/test/maestro:6a3ea4dd6de4dcc0f449e4db
history: > ✅ > ❌ > ✅
- kselftest.timers
last run: https://d.kernelci.org/test/maestro:6a3e9bc66de4dcc0f44936ea
history: > ❌ > ✅ > ❌ > ✅ > ✅
- kselftest.timers.timers_rtcpie
last run: https://d.kernelci.org/test/maestro:6a3eaaa36de4dcc0f44a4951
history: > ❌ > ✅ > ❌ > ✅
> Config: defconfig+arm64-chromebook+kselftest
- Architecture/compiler: arm64/gcc-14
- kselftest.gpio
last run: https://d.kernelci.org/test/maestro:6a3ebae86de4dcc0f44ab455
history: > ❌ > ❌ > ✅ > ❌ > ❌
Hardware: cd8180-orion-o6
> Config: defconfig+netdev+nfs-root-boot+kselftest
- Architecture/compiler: arm64/gcc-14
- kselftest.arm64
last run: https://d.kernelci.org/test/maestro:6a3e9d296de4dcc0f4495d9e
history: > ✅ > ❌ > ✅ > ✅ > ✅
- ltp
last run: https://d.kernelci.org/test/maestro:6a3e9d296de4dcc0f4495d95
history: > ✅ > ❌ > ✅ > ✅ > ✅
Hardware: dell-latitude-3445-7520c-skyrim
> Config: x86_64_defconfig+lab-setup+x86-board+kselftest
- Architecture/compiler: x86_64/gcc-14
- kselftest.cpufreq.suspend
last run: https://d.kernelci.org/test/maestro:6a3e971f6de4dcc0f448cfb5
history: > ✅ > ❌ > ✅ > ✅ > ✅
- kselftest.cpufreq.suspend.cpufreq_main_sh
last run: https://d.kernelci.org/test/maestro:6a3e98b06de4dcc0f448e99a
history: > ✅ > ❌ > ✅ > ✅ > ✅
Hardware: imx6dl-udoo
> Config: multi_v7_defconfig
- Architecture/compiler: arm/gcc-14
- boot
last run: https://d.kernelci.org/test/maestro:6a3e9e406de4dcc0f44989e8
history: > ⚠️ > ✅ > ✅ > ✅ > ✅
Hardware: mt8183-kukui-jacuzzi-juniper-sku16
> Config: defconfig+lab-setup+arm64-chromebook+CONFIG_MODULE_COMPRESS=n+CONFIG_MODULE_COMPRESS_NONE=y
- Architecture/compiler: arm64/gcc-14
- kselftest.dt.dt_test_unprobed_devices_sh_soc_dma-controller0_14001000
last run: https://d.kernelci.org/test/maestro:6a3e9de86de4dcc0f4497ddc
history: > ✅ > ❌ > ✅ > ✅ > ✅
- kselftest.dt.dt_test_unprobed_devices_sh_soc_i2c_11008000_anx7625_58_aux-bus_panel
last run: https://d.kernelci.org/test/maestro:6a3e9de86de4dcc0f4497dd0
history: > ✅ > ❌ > ✅ > ✅ > ✅
- kselftest.dt.dt_test_unprobed_devices_sh_soc_ovl_14008000
last run: https://d.kernelci.org/test/maestro:6a3e9de76de4dcc0f4497db4
history: > ✅ > ❌ > ✅ > ✅ > ✅
- kselftest.dt.dt_test_unprobed_devices_sh_soc_ovl_14009000
last run: https://d.kernelci.org/test/maestro:6a3e9de76de4dcc0f4497db3
history: > ✅ > ❌ > ✅ > ✅ > ✅
- kselftest.dt.dt_test_unprobed_devices_sh_soc_ovl_1400a000
last run: https://d.kernelci.org/test/maestro:6a3e9de76de4dcc0f4497db2
history: > ✅ > ❌ > ✅ > ✅ > ✅
- kselftest.dt.dt_test_unprobed_devices_sh_soc_rdma_1400b000
last run: https://d.kernelci.org/test/maestro:6a3e9de76de4dcc0f4497da7
history: > ✅ > ❌ > ✅ > ✅ > ✅
- kselftest.dt.dt_test_unprobed_devices_sh_soc_rdma_1400c000
last run: https://d.kernelci.org/test/maestro:6a3e9de76de4dcc0f4497da6
history: > ✅ > ❌ > ✅ > ✅ > ✅
This branch has 1 pre-existing build issues. See details in the dashboard.
Sent every day if there were changes in the past 24 hours.
Legend: ✅ PASS ❌ FAIL ⚠️ INCONCLUSIVE
--
This is an experimental report format. Please send feedback in!
Talk to us at kernelci@lists.linux.dev
Made with love by the KernelCI team - https://kernelci.org
^ permalink raw reply
* Re: [regression] synaptics-rmi4: Failed to read the Control Register Descriptor: EIO
From: Dmitry Torokhov @ 2026-06-26 21:18 UTC (permalink / raw)
To: David Heidelberg; +Cc: linux-input, Linux Next Mailing List
In-Reply-To: <de6d34b7-619c-46bd-a6e3-a3917b318571@ixit.cz>
Hi David,
On Fri, Jun 26, 2026 at 11:09:54PM +0200, David Heidelberg wrote:
> With next-20260626 without any additional patches, the synaptics fails on
> OnePlus 6T with:
>
> ```
> [ 16.620292] rmi4_i2c 12-0020: registering I2C-connected sensor
> [ 16.857617] rmi4_f01 rmi4-00.fn01: found RMI device, manufacturer:
> Synaptics, product: S3706B, fw id: 2852315
> [ 16.867324] rmi4_f12 rmi4-00.fn12: Failed to read the Control Register
> Descriptor: -5
> [ 16.867338] rmi4_f12 rmi4-00.fn12: probe with driver rmi4_f12 failed with
> error -5
> ```
Yes, at least a98518e72439 "Input: rmi4 - fix register descriptor address
calculation" is wrong and needs to be reverted.
Thanks.
--
Dmitry
^ permalink raw reply
* [regression] synaptics-rmi4: Failed to read the Control Register Descriptor: EIO
From: David Heidelberg @ 2026-06-26 21:09 UTC (permalink / raw)
To: linux-input, Dmitry Torokhov; +Cc: Linux Next Mailing List
With next-20260626 without any additional patches, the synaptics fails on
OnePlus 6T with:
```
[ 16.620292] rmi4_i2c 12-0020: registering I2C-connected sensor
[ 16.857617] rmi4_f01 rmi4-00.fn01: found RMI device, manufacturer: Synaptics,
product: S3706B, fw id: 2852315
[ 16.867324] rmi4_f12 rmi4-00.fn12: Failed to read the Control Register
Descriptor: -5
[ 16.867338] rmi4_f12 rmi4-00.fn12: probe with driver rmi4_f12 failed with
error -5
```
I assume it's due to refactoring. My best guess it's signed/unsigned 32/64bit
type changes, but since I haven't figured it out within reasonable timeframe.
David
^ permalink raw reply
* linux-next: Tree for Jun 26
From: Mark Brown @ 2026-06-26 14:26 UTC (permalink / raw)
To: Linux Next Mailing List; +Cc: Linux Kernel Mailing List
[-- Attachment #1: Type: text/plain, Size: 1737 bytes --]
Hi all,
The merge window is open, so please to not addd any v7.2 material
to your linux-next included branches until after the merge window closes.
Changes since 20260625:
None.
Non-merge commits (relative to Linus' tree): 1105
1119 files changed, 52070 insertions(+), 22217 deletions(-)
----------------------------------------------------------------------------
I have created today's linux-next tree at
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
(patches at https://www.kernel.org/pub/linux/kernel/next/ ). If you
are tracking the linux-next tree using git, you should not use "git pull"
to do so as that will try to merge the new linux-next release with the
old one. You should use "git fetch" and checkout or reset to the new
master.
You can see which trees have been included by looking in the Next/Trees
file in the source. There is also the merge.log file in the Next
directory. Between each merge, the tree was built with a defconfig
for arm64, an allmodconfig for x86_64, a multi_v7_defconfig for arm,
an arm64 build of various kselftests, a KUnit build and run on arm64,
and a native build of tools/perf. After the final fixups (if any), I do
an x86_64 modules_install followed by builds for x86_64 allnoconfig,
arm64 allyesconfig, powerpc allnoconfig (32 and 64 bit),
ppc44x_defconfig and pseries_le_defconfig and i386, s390, sparc and
sparc64 defconfig and htmldocs.
Below is a summary of the state of the merge.
I am currently merging 425 trees (counting Linus' and 131 trees of bug
fix patches pending for the current release).
Stats about the size of the tree over time can be seen at
http://neuling.org/linux-next-size.html .
Thanks to Paul Gortmaker for triage and bug fixes.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
^ permalink raw reply
* [STATUS] next/master - 30ffa8de54e5cc80d93fd211ca134d1764a7011f
From: KernelCI bot @ 2026-06-26 2:30 UTC (permalink / raw)
To: kernelci-results; +Cc: linux-next
Hello,
Status summary for next/master
Dashboard:
https://d.kernelci.org/c/next/master/30ffa8de54e5cc80d93fd211ca134d1764a7011f/
giturl: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
branch: master
commit hash: 30ffa8de54e5cc80d93fd211ca134d1764a7011f
origin: maestro
test start time: 2026-06-25 17:02:20.204000+00:00
Builds: 66 ✅ 2 ❌ 0 ⚠️
Boots: 163 ✅ 4 ❌ 0 ⚠️
Tests: 26856 ✅ 4945 ❌ 3474 ⚠️
### POSSIBLE REGRESSIONS
Hardware: glymur-crd
> Config: defconfig+lab-setup+kselftest
- Architecture/compiler: arm64/gcc-14
- kselftest.dt.dt_test_unprobed_devices_sh_soc_0_pci_1c00000
last run: https://d.kernelci.org/test/maestro:6a3d90366de4dcc0f4447c4d
history: > ✅ > ❌
Hardware: qcs8300-ride
> Config: defconfig+lab-setup+kselftest
- Architecture/compiler: arm64/gcc-14
- kselftest.dt.dt_test_unprobed_devices_sh_soc_0_pci_1c00000_pcie_0_wifi_0
last run: https://d.kernelci.org/test/maestro:6a3da1f96de4dcc0f4454c20
history: > ✅ > ❌
### FIXED REGRESSIONS
Hardware: bcm2711-rpi-4-b
> Config: defconfig+lab-setup+kselftest
- Architecture/compiler: arm64/gcc-14
- kselftest.dt
last run: https://d.kernelci.org/test/maestro:6a3d70626de4dcc0f44259cb
history: > ❌ > ❌ > ✅
- kselftest.dt.dt_test_unprobed_devices_sh
last run: https://d.kernelci.org/test/maestro:6a3d7b836de4dcc0f4439054
history: > ❌ > ❌ > ✅
- kselftest.dt.dt_test_unprobed_devices_sh_gpu
last run: https://d.kernelci.org/test/maestro:6a3d7b836de4dcc0f4439088
history: > ❌ > ❌ > ✅
### UNSTABLE TESTS
Hardware: qcs6490-rb3gen2
> Config: defconfig+lab-setup+kselftest
- Architecture/compiler: arm64/gcc-14
- kselftest.breakpoints
last run: https://d.kernelci.org/test/maestro:6a3d6d7e6de4dcc0f4421d8a
history: > ❌ > ❌ > ❌ > ✅ > ❌
Hardware: qcs8300-ride
> Config: defconfig+lab-setup+kselftest
- Architecture/compiler: arm64/gcc-14
- kselftest.coredump
last run: https://d.kernelci.org/test/maestro:6a3d6da46de4dcc0f4421f34
history: > ❌ > ❌ > ❌ > ✅ > ❌
- kselftest.dt.dt_test_unprobed_devices_sh_soc_0_ethernet_23040000_mdio_phy_8
last run: https://d.kernelci.org/test/maestro:6a3da1f96de4dcc0f4454c5c
history: > ✅ > ⚠️
- kselftest.timers
last run: https://d.kernelci.org/test/maestro:6a3d6de46de4dcc0f442235b
history: > ✅ > ❌ > ✅ > ❌ > ✅
> Config: defconfig+arm64-chromebook+kselftest
- Architecture/compiler: arm64/gcc-14
- kselftest.gpio
last run: https://d.kernelci.org/test/maestro:6a3d6b766de4dcc0f441d8f8
history: > ❌ > ❌ > ❌ > ✅ > ❌
Hardware: bcm2711-rpi-4-b
> Config: defconfig+lab-setup+kselftest
- Architecture/compiler: arm64/gcc-14
- boot
last run: https://d.kernelci.org/test/maestro:6a3d702e6de4dcc0f44257a7
history: > ⚠️ > ✅ > ✅ > ✅ > ✅
Hardware: beaglebone-black
> Config: multi_v7_defconfig
- Architecture/compiler: arm/gcc-14
- boot
last run: https://d.kernelci.org/test/maestro:6a3d6cf06de4dcc0f441e40b
history: > ⚠️ > ✅ > ✅ > ✅ > ✅
Hardware: cd8180-orion-o6
> Config: defconfig+lab-setup+kselftest
- Architecture/compiler: arm64/gcc-14
- boot
last run: https://d.kernelci.org/test/maestro:6a3d6fda6de4dcc0f44252db
history: > ⚠️ > ✅ > ✅
> Config: defconfig+netdev+nfs-root-boot+kselftest
- Architecture/compiler: arm64/gcc-14
- kselftest.arm64
last run: https://d.kernelci.org/test/maestro:6a3d6fd46de4dcc0f44252b3
history: > ⚠️ > ✅ > ❌ > ✅ > ✅
- ltp
last run: https://d.kernelci.org/test/maestro:6a3d6fd36de4dcc0f44252aa
history: > ⚠️ > ✅ > ❌ > ✅ > ✅
Hardware: dell-latitude-3445-7520c-skyrim
> Config: x86_64_defconfig+lab-setup+x86-board+kselftest
- Architecture/compiler: x86_64/gcc-14
- kselftest.cpufreq.suspend
last run: https://d.kernelci.org/test/maestro:6a3d71f66de4dcc0f44272bc
history: > ✅ > ✅ > ❌ > ✅ > ✅
- kselftest.cpufreq.suspend.cpufreq_main_sh
last run: https://d.kernelci.org/test/maestro:6a3d73176de4dcc0f442aa73
history: > ✅ > ✅ > ❌ > ✅ > ✅
Hardware: exynos850-e850-96
> Config: defconfig+lab-setup+kselftest
- Architecture/compiler: arm64/gcc-14
- boot
last run: https://d.kernelci.org/test/maestro:6a3d6fda6de4dcc0f44252de
history: > ⚠️ > ✅ > ✅
- kselftest.arm64
last run: https://d.kernelci.org/test/maestro:6a3d6fdc6de4dcc0f4425376
history: > ⚠️ > ✅ > ✅
- kselftest.breakpoints
last run: https://d.kernelci.org/test/maestro:6a3d6fdc6de4dcc0f4425379
history: > ⚠️ > ✅ > ✅
- ltp
last run: https://d.kernelci.org/test/maestro:6a3d6fdb6de4dcc0f4425373
history: > ⚠️ > ✅ > ✅
Hardware: imx6dl-riotboard
> Config: multi_v7_defconfig
- Architecture/compiler: arm/gcc-14
- boot
last run: https://d.kernelci.org/test/maestro:6a3d6d0d6de4dcc0f441e8c1
history: > ⚠️ > ✅ > ✅ > ✅ > ✅
Hardware: mt8183-kukui-jacuzzi-juniper-sku16
> Config: defconfig+lab-setup+arm64-chromebook+CONFIG_MODULE_COMPRESS=n+CONFIG_MODULE_COMPRESS_NONE=y
- Architecture/compiler: arm64/gcc-14
- kselftest.dt.dt_test_unprobed_devices_sh_soc_dma-controller0_14001000
last run: https://d.kernelci.org/test/maestro:6a3d84d26de4dcc0f44422f4
history: > ✅ > ✅ > ❌ > ✅ > ✅
- kselftest.dt.dt_test_unprobed_devices_sh_soc_i2c_11008000_anx7625_58_aux-bus_panel
last run: https://d.kernelci.org/test/maestro:6a3d84d26de4dcc0f44422e8
history: > ✅ > ✅ > ❌ > ✅ > ✅
- kselftest.dt.dt_test_unprobed_devices_sh_soc_ovl_14008000
last run: https://d.kernelci.org/test/maestro:6a3d84d26de4dcc0f44422cc
history: > ✅ > ✅ > ❌ > ✅ > ✅
- kselftest.dt.dt_test_unprobed_devices_sh_soc_ovl_14009000
last run: https://d.kernelci.org/test/maestro:6a3d84d26de4dcc0f44422cb
history: > ✅ > ✅ > ❌ > ✅ > ✅
- kselftest.dt.dt_test_unprobed_devices_sh_soc_ovl_1400a000
last run: https://d.kernelci.org/test/maestro:6a3d84d26de4dcc0f44422ca
history: > ✅ > ✅ > ❌ > ✅ > ✅
- kselftest.dt.dt_test_unprobed_devices_sh_soc_rdma_1400b000
last run: https://d.kernelci.org/test/maestro:6a3d84d26de4dcc0f44422bf
history: > ✅ > ✅ > ❌ > ✅ > ✅
- kselftest.dt.dt_test_unprobed_devices_sh_soc_rdma_1400c000
last run: https://d.kernelci.org/test/maestro:6a3d84d26de4dcc0f44422be
history: > ✅ > ✅ > ❌ > ✅ > ✅
Hardware: mt8195-cherry-tomato-r2
> Config: defconfig+lab-setup+arm64-chromebook+CONFIG_MODULE_COMPRESS=n+CONFIG_MODULE_COMPRESS_NONE=y
- Architecture/compiler: arm64/gcc-14
- kselftest.dt.dt_test_unprobed_devices_sh_mt8195-sound
last run: https://d.kernelci.org/test/maestro:6a3d73976de4dcc0f442bdbf
history: > ✅ > ❌ > ✅
- kselftest.dt.dt_test_unprobed_devices_sh_soc_dma-controller_1c104000
last run: https://d.kernelci.org/test/maestro:6a3d73976de4dcc0f442bd5c
history: > ✅ > ❌ > ✅
- kselftest.dt.dt_test_unprobed_devices_sh_soc_dma-controller_1c105000
last run: https://d.kernelci.org/test/maestro:6a3d73976de4dcc0f442bd5b
history: > ✅ > ❌ > ✅
- kselftest.dt.dt_test_unprobed_devices_sh_soc_dma-controller_1c106000
last run: https://d.kernelci.org/test/maestro:6a3d73976de4dcc0f442bd5a
history: > ✅ > ❌ > ✅
- kselftest.dt.dt_test_unprobed_devices_sh_soc_dma-controller_1c107000
last run: https://d.kernelci.org/test/maestro:6a3d73976de4dcc0f442bd59
history: > ✅ > ❌ > ✅
- kselftest.dt.dt_test_unprobed_devices_sh_soc_dma-controller_1c108000
last run: https://d.kernelci.org/test/maestro:6a3d73976de4dcc0f442bd58
history: > ✅ > ❌ > ✅
- kselftest.dt.dt_test_unprobed_devices_sh_soc_dma-controller_1c109000
last run: https://d.kernelci.org/test/maestro:6a3d73976de4dcc0f442bd57
history: > ✅ > ❌ > ✅
- kselftest.dt.dt_test_unprobed_devices_sh_soc_dma-controller_1c10a000
last run: https://d.kernelci.org/test/maestro:6a3d73976de4dcc0f442bd56
history: > ✅ > ❌ > ✅
- kselftest.dt.dt_test_unprobed_devices_sh_soc_dma-controller_1c10b000
last run: https://d.kernelci.org/test/maestro:6a3d73976de4dcc0f442bd55
history: > ✅ > ❌ > ✅
- kselftest.dt.dt_test_unprobed_devices_sh_soc_dp-intf_1c015000
last run: https://d.kernelci.org/test/maestro:6a3d73976de4dcc0f442bd54
history: > ✅ > ❌ > ✅
- kselftest.dt.dt_test_unprobed_devices_sh_soc_dp-intf_1c113000
last run: https://d.kernelci.org/test/maestro:6a3d73976de4dcc0f442bd53
history: > ✅ > ❌ > ✅
- kselftest.dt.dt_test_unprobed_devices_sh_soc_hdr-engine_1c114000
last run: https://d.kernelci.org/test/maestro:6a3d73976de4dcc0f442bd4a
history: > ✅ > ❌ > ✅
- kselftest.dt.dt_test_unprobed_devices_sh_soc_jpeg-decoder_1a040000
last run: https://d.kernelci.org/test/maestro:6a3d73976de4dcc0f442bd39
history: > ✅ > ❌ > ✅
- kselftest.dt.dt_test_unprobed_devices_sh_soc_jpeg-decoder_1a040000_jpgdec_0_0
last run: https://d.kernelci.org/test/maestro:6a3d73976de4dcc0f442bd38
history: > ✅ > ❌ > ✅
- kselftest.dt.dt_test_unprobed_devices_sh_soc_jpeg-decoder_1a040000_jpgdec_0_10000
last run: https://d.kernelci.org/test/maestro:6a3d73976de4dcc0f442bd37
history: > ✅ > ❌ > ✅
- kselftest.dt.dt_test_unprobed_devices_sh_soc_jpeg-decoder_1a040000_jpgdec_1_0
last run: https://d.kernelci.org/test/maestro:6a3d73976de4dcc0f442bd36
history: > ✅ > ❌ > ✅
- kselftest.dt.dt_test_unprobed_devices_sh_soc_jpeg-encoder_1a030000
last run: https://d.kernelci.org/test/maestro:6a3d73976de4dcc0f442bd35
history: > ✅ > ❌ > ✅
- kselftest.dt.dt_test_unprobed_devices_sh_soc_jpeg-encoder_1a030000_jpgenc_0_0
last run: https://d.kernelci.org/test/maestro:6a3d73976de4dcc0f442bd34
history: > ✅ > ❌ > ✅
- kselftest.dt.dt_test_unprobed_devices_sh_soc_jpeg-encoder_1a030000_jpgenc_1_0
last run: https://d.kernelci.org/test/maestro:6a3d73976de4dcc0f442bd33
history: > ✅ > ❌ > ✅
- kselftest.dt.dt_test_unprobed_devices_sh_soc_ovl_1c000000
last run: https://d.kernelci.org/test/maestro:6a3d73976de4dcc0f442bd0a
history: > ✅ > ❌ > ✅
- kselftest.dt.dt_test_unprobed_devices_sh_soc_rdma_1c002000
last run: https://d.kernelci.org/test/maestro:6a3d73976de4dcc0f442bcff
history: > ✅ > ❌ > ✅
- kselftest.dt.dt_test_unprobed_devices_sh_soc_video-codec_18000000
last run: https://d.kernelci.org/test/maestro:6a3d73976de4dcc0f442bde2
history: > ✅ > ❌ > ✅
- kselftest.dt.dt_test_unprobed_devices_sh_soc_video-codec_18000000_video-codec_10000
last run: https://d.kernelci.org/test/maestro:6a3d73976de4dcc0f442bde1
history: > ✅ > ❌ > ✅
- kselftest.dt.dt_test_unprobed_devices_sh_soc_video-codec_18000000_video-codec_2000
last run: https://d.kernelci.org/test/maestro:6a3d73976de4dcc0f442bde0
history: > ✅ > ❌ > ✅
- kselftest.dt.dt_test_unprobed_devices_sh_soc_video-codec_18000000_video-codec_25000
last run: https://d.kernelci.org/test/maestro:6a3d73976de4dcc0f442bddf
history: > ✅ > ❌ > ✅
- kselftest.dt.dt_test_unprobed_devices_sh_soc_video-codec_1a020000
last run: https://d.kernelci.org/test/maestro:6a3d73976de4dcc0f442bdde
history: > ✅ > ❌ > ✅
This branch has 1 pre-existing build issues. See details in the dashboard.
Sent every day if there were changes in the past 24 hours.
Legend: ✅ PASS ❌ FAIL ⚠️ INCONCLUSIVE
--
This is an experimental report format. Please send feedback in!
Talk to us at kernelci@lists.linux.dev
Made with love by the KernelCI team - https://kernelci.org
^ permalink raw reply
* linux-next: Tree for Jun 25
From: Mark Brown @ 2026-06-25 16:52 UTC (permalink / raw)
To: Linux Next Mailing List; +Cc: Linux Kernel Mailing List
[-- Attachment #1: Type: text/plain, Size: 1771 bytes --]
Hi all,
The merge window is open, so please to not addd any v7.2 material
to your linux-next included branches until after the merge window closes.
Changes since 20260624:
The arm64 tree lost it's build failure.
Non-merge commits (relative to Linus' tree): 1449
1463 files changed, 67636 insertions(+), 24716 deletions(-)
----------------------------------------------------------------------------
I have created today's linux-next tree at
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
(patches at https://www.kernel.org/pub/linux/kernel/next/ ). If you
are tracking the linux-next tree using git, you should not use "git pull"
to do so as that will try to merge the new linux-next release with the
old one. You should use "git fetch" and checkout or reset to the new
master.
You can see which trees have been included by looking in the Next/Trees
file in the source. There is also the merge.log file in the Next
directory. Between each merge, the tree was built with a defconfig
for arm64, an allmodconfig for x86_64, a multi_v7_defconfig for arm,
an arm64 build of various kselftests, a KUnit build and run on arm64,
and a native build of tools/perf. After the final fixups (if any), I do
an x86_64 modules_install followed by builds for x86_64 allnoconfig,
arm64 allyesconfig, powerpc allnoconfig (32 and 64 bit),
ppc44x_defconfig and pseries_le_defconfig and i386, s390, sparc and
sparc64 defconfig and htmldocs.
Below is a summary of the state of the merge.
I am currently merging 425 trees (counting Linus' and 131 trees of bug
fix patches pending for the current release).
Stats about the size of the tree over time can be seen at
http://neuling.org/linux-next-size.html .
Thanks to Paul Gortmaker for triage and bug fixes.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
^ permalink raw reply
* linux-next: Tree for Jun 24
From: Mark Brown @ 2026-06-24 14:42 UTC (permalink / raw)
To: Linux Next Mailing List; +Cc: Linux Kernel Mailing List
[-- Attachment #1: Type: text/plain, Size: 1819 bytes --]
Hi all,
The merge window is open, so please to not addd any v7.2 material
to your linux-next included branches until after the merge window closes.
Changes since 20260622:
The arm64 tree acquired a build failure, I used the version from
next-20260623 instead.
Non-merge commits (relative to Linus' tree): 1592
1507 files changed, 65562 insertions(+), 21462 deletions(-)
----------------------------------------------------------------------------
I have created today's linux-next tree at
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
(patches at https://www.kernel.org/pub/linux/kernel/next/ ). If you
are tracking the linux-next tree using git, you should not use "git pull"
to do so as that will try to merge the new linux-next release with the
old one. You should use "git fetch" and checkout or reset to the new
master.
You can see which trees have been included by looking in the Next/Trees
file in the source. There is also the merge.log file in the Next
directory. Between each merge, the tree was built with a defconfig
for arm64, an allmodconfig for x86_64, a multi_v7_defconfig for arm,
an arm64 build of various kselftests, a KUnit build and run on arm64,
and a native build of tools/perf. After the final fixups (if any), I do
an x86_64 modules_install followed by builds for x86_64 allnoconfig,
arm64 allyesconfig, powerpc allnoconfig (32 and 64 bit),
ppc44x_defconfig and pseries_le_defconfig and i386, s390, sparc and
sparc64 defconfig and htmldocs.
Below is a summary of the state of the merge.
I am currently merging 425 trees (counting Linus' and 131 trees of bug
fix patches pending for the current release).
Stats about the size of the tree over time can be seen at
http://neuling.org/linux-next-size.html .
Thanks to Paul Gortmaker for triage and bug fixes.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
^ permalink raw reply
* Re: linux-next: build failure after merge of the arm64 tree
From: Will Deacon @ 2026-06-24 13:05 UTC (permalink / raw)
To: Mark Brown
Cc: Catalin Marinas, Mark Rutland, Marc Zyngier, Arnd Bergmann,
Linux Kernel Mailing List, Linux Next Mailing List
In-Reply-To: <ajvGS7UBpWzJtzkw@sirena.org.uk>
On Wed, Jun 24, 2026 at 12:58:03PM +0100, Mark Brown wrote:
> Hi all,
>
> After merging the arm64 tree, today's linux-next build
> (arm64 kselftest) failed like this:
>
> CC iommufd_fail_nth
> CC iommufd
> CC msgque
> CC ir_loopback
> CC kcmp_test
> CC harness-selftest
> In file included from /usr/include/aarch64-linux-gnu/bits/sigcontext.h:30,
> from /usr/include/signal.h:301,
> from include/test_util.h:12,
> from lib/io.c:8:
> /tmp/next/arm64_kselftest/usr/include/asm/sigcontext.h:81:9: error:
> unknown type name '__u128'; did you mean '__u32'?
> 81 | __u128 vregs[32];
> | ^~~~~~ __u32
> cc1: note: unrecognized command-line option
> '-Wno-gnu-variable-sized-type-not-at-end' may have been intended
> to silence earlier diagnostics make[1]: *** [Makefile.kvm:347:
> /tmp/next/arm64_kselftest/kselftest/kvm/lib/io.o] Error 1 make[1]:
Thanks, Mark. I also got a similar report from test robot [1], so I'll
just drop this change until I've figured out the root cause.
Will
[1] https://lore.kernel.org/r/202606240441.7eZ1TIRM-lkp@intel.com
^ permalink raw reply
* linux-next: build failure after merge of the arm64 tree
From: Mark Brown @ 2026-06-24 11:58 UTC (permalink / raw)
To: Catalin Marinas, Will Deacon
Cc: Mark Rutland, Marc Zyngier, Arnd Bergmann,
Linux Kernel Mailing List, Linux Next Mailing List
[-- Attachment #1: Type: text/plain, Size: 112848 bytes --]
Hi all,
After merging the arm64 tree, today's linux-next build
(arm64 kselftest) failed like this:
CC iommufd_fail_nth
CC iommufd
CC msgque
CC ir_loopback
CC kcmp_test
CC harness-selftest
In file included from /usr/include/aarch64-linux-gnu/bits/sigcontext.h:30,
from /usr/include/signal.h:301,
from include/test_util.h:12,
from lib/io.c:8:
/tmp/next/arm64_kselftest/usr/include/asm/sigcontext.h:81:9: error:
unknown type name '__u128'; did you mean '__u32'?
81 | __u128 vregs[32];
| ^~~~~~ __u32
cc1: note: unrecognized command-line option
'-Wno-gnu-variable-sized-type-not-at-end' may have been intended
to silence earlier diagnostics make[1]: *** [Makefile.kvm:347:
/tmp/next/arm64_kselftest/kselftest/kvm/lib/io.o] Error 1 make[1]:
*** Waiting for unfinished jobs.... In file included from
/usr/include/aarch64-linux-gnu/bits/sigcontext.h:30,
from /usr/include/signal.h:301,
from include/test_util.h:12,
from lib/assert.c:7:
/tmp/next/arm64_kselftest/usr/include/asm/sigcontext.h:81:9: error:
unknown type name '__u128'; did you mean '__u32'?
81 | __u128 vregs[32];
| ^~~~~~ __u32
cc1: note: unrecognized command-line option
'-Wno-gnu-variable-sized-type-not-at-end' may have been intended
to silence earlier diagnostics make[1]: *** [Makefile.kvm:347:
/tmp/next/arm64_kselftest/kselftest/kvm/lib/assert.o] Error 1 In file
included from /usr/include/aarch64-linux-gnu/bits/sigcontext.h:30,
from /usr/include/signal.h:301,
from include/test_util.h:12,
from include/lru_gen_util.h:14,
from lib/lru_gen_util.c:8:
/tmp/next/arm64_kselftest/usr/include/asm/sigcontext.h:81:9: error:
unknown type name '__u128'; did you mean '__u32'?
81 | __u128 vregs[32];
| ^~~~~~ __u32
cc1: note: unrecognized command-line option
'-Wno-gnu-variable-sized-type-not-at-end' may have been intended
to silence earlier diagnostics make[1]: *** [Makefile.kvm:347:
/tmp/next/arm64_kselftest/kselftest/kvm/lib/lru_gen_util.o] Error 1 In
file included from /usr/include/aarch64-linux-gnu/bits/sigcontext.h:30,
from /usr/include/signal.h:301,
from include/test_util.h:12,
from lib/test_util.c:19:
/tmp/next/arm64_kselftest/usr/include/asm/sigcontext.h:81:9: error:
unknown type name '__u128'; did you mean '__u32'?
81 | __u128 vregs[32];
| ^~~~~~ __u32
cc1: note: unrecognized command-line option
'-Wno-gnu-variable-sized-type-not-at-end' may have been intended
to silence earlier diagnostics make[1]: *** [Makefile.kvm:347:
/tmp/next/arm64_kselftest/kselftest/kvm/lib/test_util.o] Error 1 In file
included from /usr/include/aarch64-linux-gnu/bits/sigcontext.h:30,
from /usr/include/signal.h:301,
from include/test_util.h:12,
from lib/sparsebit.c:158:
/tmp/next/arm64_kselftest/usr/include/asm/sigcontext.h:81:9: error:
unknown type name '__u128'; did you mean '__u32'?
81 | __u128 vregs[32];
| ^~~~~~ __u32
cc1: note: unrecognized command-line option
'-Wno-gnu-variable-sized-type-not-at-end' may have been intended
to silence earlier diagnostics make[1]: *** [Makefile.kvm:347:
/tmp/next/arm64_kselftest/kselftest/kvm/lib/sparsebit.o] Error 1 In file
included from /usr/include/aarch64-linux-gnu/bits/sigcontext.h:30,
from /usr/include/signal.h:301,
from /tmp/next/build/tools/testing/selftests/cgroup/lib/cgroup_util.c:9:
/tmp/next/arm64_kselftest/usr/include/asm/sigcontext.h:81:9: error:
unknown type name '__u128'; did you mean '__u32'?
81 | __u128 vregs[32];
| ^~~~~~ __u32
cc1: note: unrecognized command-line option
'-Wno-gnu-variable-sized-type-not-at-end' may have been intended to
silence earlier diagnostics make[1]: *** [../cgroup/lib/libcgroup.mk:17:
/tmp/next/arm64_kselftest/kselftest/kvm/lib/cgroup_util.o] Error 1 In
file included from /usr/include/aarch64-linux-gnu/bits/sigcontext.h:30,
from /usr/include/signal.h:301,
from include/test_util.h:12,
from lib/elf.c:8:
/tmp/next/arm64_kselftest/usr/include/asm/sigcontext.h:81:9: error:
unknown type name '__u128'; did you mean '__u32'?
81 | __u128 vregs[32];
| ^~~~~~ __u32
In file included from /tmp/next/arm64_kselftest/usr/include/asm/kvm.h:37,
from /tmp/next/arm64_kselftest/usr/include/linux/kvm.h:16,
from include/kvm_util.h:14,
from lib/elf.c:13:
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:96:9: error: unknown
type name '__u128'; did you mean '__u32'?
96 | __u128 vregs[32];
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:261:9: error: unknown
type name '__u128'; did you mean '__u32'?
261 | __u128 apiakey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:262:9: error: unknown
type name '__u128'; did you mean '__u32'?
262 | __u128 apibkey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:263:9: error: unknown
type name '__u128'; did you mean '__u32'?
263 | __u128 apdakey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:264:9: error: unknown
type name '__u128'; did you mean '__u32'?
264 | __u128 apdbkey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:268:9: error: unknown
type name '__u128'; did you mean '__u32'?
268 | __u128 apgakey;
| ^~~~~~ __u32
cc1: note: unrecognized command-line option
'-Wno-gnu-variable-sized-type-not-at-end' may have been intended
to silence earlier diagnostics make[1]: *** [Makefile.kvm:347:
/tmp/next/arm64_kselftest/kselftest/kvm/lib/elf.o] Error 1 In file
included from /usr/include/aarch64-linux-gnu/bits/sigcontext.h:30,
from /usr/include/signal.h:301,
from include/test_util.h:12,
from include/kvm_util.h:8,
from demand_paging_test.c:17:
/tmp/next/arm64_kselftest/usr/include/asm/sigcontext.h:81:9: error:
unknown type name '__u128'; did you mean '__u32'?
81 | __u128 vregs[32];
| ^~~~~~ __u32
In file included from /tmp/next/arm64_kselftest/usr/include/asm/kvm.h:37,
from /tmp/next/arm64_kselftest/usr/include/linux/kvm.h:16,
from include/kvm_util.h:14:
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:96:9: error: unknown
type name '__u128'; did you mean '__u32'?
96 | __u128 vregs[32];
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:261:9: error: unknown
type name '__u128'; did you mean '__u32'?
261 | __u128 apiakey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:262:9: error: unknown
type name '__u128'; did you mean '__u32'?
262 | __u128 apibkey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:263:9: error: unknown
type name '__u128'; did you mean '__u32'?
263 | __u128 apdakey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:264:9: error: unknown
type name '__u128'; did you mean '__u32'?
264 | __u128 apdbkey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:268:9: error: unknown
type name '__u128'; did you mean '__u32'?
268 | __u128 apgakey;
| ^~~~~~ __u32
cc1: note: unrecognized command-line option
'-Wno-gnu-variable-sized-type-not-at-end' may have been intended
to silence earlier diagnostics make[1]: *** [Makefile.kvm:332:
/tmp/next/arm64_kselftest/kselftest/kvm/demand_paging_test.o] Error 1
In file included from /usr/include/aarch64-linux-gnu/bits/sigcontext.h:30,
from /usr/include/signal.h:301,
from include/test_util.h:12,
from lib/guest_sprintf.c:2:
/tmp/next/arm64_kselftest/usr/include/asm/sigcontext.h:81:9: error:
unknown type name '__u128'; did you mean '__u32'?
81 | __u128 vregs[32];
| ^~~~~~ __u32
In file included from /tmp/next/arm64_kselftest/usr/include/asm/kvm.h:37,
from /tmp/next/arm64_kselftest/usr/include/linux/kvm.h:16,
from include/kvm_util.h:14,
from lib/guest_sprintf.c:3:
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:96:9: error: unknown
type name '__u128'; did you mean '__u32'?
96 | __u128 vregs[32];
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:261:9: error: unknown
type name '__u128'; did you mean '__u32'?
261 | __u128 apiakey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:262:9: error: unknown
type name '__u128'; did you mean '__u32'?
262 | __u128 apibkey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:263:9: error: unknown
type name '__u128'; did you mean '__u32'?
263 | __u128 apdakey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:264:9: error: unknown
type name '__u128'; did you mean '__u32'?
264 | __u128 apdbkey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:268:9: error: unknown
type name '__u128'; did you mean '__u32'?
268 | __u128 apgakey;
| ^~~~~~ __u32
cc1: note: unrecognized command-line option
'-Wno-gnu-variable-sized-type-not-at-end' may have been intended
to silence earlier diagnostics make[1]: *** [Makefile.kvm:347:
/tmp/next/arm64_kselftest/kselftest/kvm/lib/guest_sprintf.o] Error 1 In
file included from /usr/include/aarch64-linux-gnu/bits/sigcontext.h:30,
from /usr/include/signal.h:301,
from include/test_util.h:12,
from include/kvm_util.h:8,
from lib/arm64/ucall.c:7:
/tmp/next/arm64_kselftest/usr/include/asm/sigcontext.h:81:9: error:
unknown type name '__u128'; did you mean '__u32'?
81 | __u128 vregs[32];
| ^~~~~~ __u32
In file included from /tmp/next/arm64_kselftest/usr/include/asm/kvm.h:37,
from /tmp/next/arm64_kselftest/usr/include/linux/kvm.h:16,
from include/kvm_util.h:14:
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:96:9: error: unknown
type name '__u128'; did you mean '__u32'?
96 | __u128 vregs[32];
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:261:9: error: unknown
type name '__u128'; did you mean '__u32'?
261 | __u128 apiakey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:262:9: error: unknown
type name '__u128'; did you mean '__u32'?
262 | __u128 apibkey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:263:9: error: unknown
type name '__u128'; did you mean '__u32'?
263 | __u128 apdakey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:264:9: error: unknown
type name '__u128'; did you mean '__u32'?
264 | __u128 apdbkey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:268:9: error: unknown
type name '__u128'; did you mean '__u32'?
268 | __u128 apgakey;
| ^~~~~~ __u32
cc1: note: unrecognized command-line option
'-Wno-gnu-variable-sized-type-not-at-end' may have been intended
to silence earlier diagnostics make[1]: *** [Makefile.kvm:347:
/tmp/next/arm64_kselftest/kselftest/kvm/lib/arm64/ucall.o] Error 1 In
file included from /usr/include/aarch64-linux-gnu/bits/sigcontext.h:30,
from /usr/include/signal.h:301,
from include/test_util.h:12,
from include/kvm_util.h:8,
from lib/ucall_common.c:6:
/tmp/next/arm64_kselftest/usr/include/asm/sigcontext.h:81:9: error:
unknown type name '__u128'; did you mean '__u32'?
81 | __u128 vregs[32];
| ^~~~~~ __u32
In file included from /tmp/next/arm64_kselftest/usr/include/asm/kvm.h:37,
from /tmp/next/arm64_kselftest/usr/include/linux/kvm.h:16,
from include/kvm_util.h:14:
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:96:9: error: unknown
type name '__u128'; did you mean '__u32'?
96 | __u128 vregs[32];
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:261:9: error: unknown
type name '__u128'; did you mean '__u32'?
261 | __u128 apiakey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:262:9: error: unknown
type name '__u128'; did you mean '__u32'?
262 | __u128 apibkey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:263:9: error: unknown
type name '__u128'; did you mean '__u32'?
263 | __u128 apdakey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:264:9: error: unknown
type name '__u128'; did you mean '__u32'?
264 | __u128 apdbkey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:268:9: error: unknown
type name '__u128'; did you mean '__u32'?
268 | __u128 apgakey;
| ^~~~~~ __u32
cc1: note: unrecognized command-line option
'-Wno-gnu-variable-sized-type-not-at-end' may have been intended
to silence earlier diagnostics make[1]: *** [Makefile.kvm:347:
/tmp/next/arm64_kselftest/kselftest/kvm/lib/ucall_common.o] Error 1 In
file included from /usr/include/aarch64-linux-gnu/bits/sigcontext.h:30,
from /usr/include/signal.h:301,
from include/test_util.h:12,
from kvm_create_max_vcpus.c:14:
/tmp/next/arm64_kselftest/usr/include/asm/sigcontext.h:81:9: error:
unknown type name '__u128'; did you mean '__u32'?
81 | __u128 vregs[32];
| ^~~~~~ __u32
In file included from /tmp/next/arm64_kselftest/usr/include/asm/kvm.h:37,
from /tmp/next/arm64_kselftest/usr/include/linux/kvm.h:16,
from include/kvm_util.h:14,
from kvm_create_max_vcpus.c:16:
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:96:9: error: unknown
type name '__u128'; did you mean '__u32'?
96 | __u128 vregs[32];
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:261:9: error: unknown
type name '__u128'; did you mean '__u32'?
261 | __u128 apiakey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:262:9: error: unknown
type name '__u128'; did you mean '__u32'?
262 | __u128 apibkey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:263:9: error: unknown
type name '__u128'; did you mean '__u32'?
263 | __u128 apdakey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:264:9: error: unknown
type name '__u128'; did you mean '__u32'?
264 | __u128 apdbkey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:268:9: error: unknown
type name '__u128'; did you mean '__u32'?
268 | __u128 apgakey;
| ^~~~~~ __u32
cc1: note: unrecognized command-line option
'-Wno-gnu-variable-sized-type-not-at-end' may have been intended
to silence earlier diagnostics make[1]: *** [Makefile.kvm:332:
/tmp/next/arm64_kselftest/kselftest/kvm/kvm_create_max_vcpus.o] Error 1
In file included from /usr/include/aarch64-linux-gnu/bits/sigcontext.h:30,
from /usr/include/signal.h:301,
from include/test_util.h:12,
from include/kvm_util.h:8,
from lib/userfaultfd_util.c:19:
/tmp/next/arm64_kselftest/usr/include/asm/sigcontext.h:81:9: error:
unknown type name '__u128'; did you mean '__u32'?
81 | __u128 vregs[32];
| ^~~~~~ __u32
In file included from /tmp/next/arm64_kselftest/usr/include/asm/kvm.h:37,
from /tmp/next/arm64_kselftest/usr/include/linux/kvm.h:16,
from include/kvm_util.h:14:
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:96:9: error: unknown
type name '__u128'; did you mean '__u32'?
96 | __u128 vregs[32];
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:261:9: error: unknown
type name '__u128'; did you mean '__u32'?
261 | __u128 apiakey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:262:9: error: unknown
type name '__u128'; did you mean '__u32'?
262 | __u128 apibkey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:263:9: error: unknown
type name '__u128'; did you mean '__u32'?
263 | __u128 apdakey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:264:9: error: unknown
type name '__u128'; did you mean '__u32'?
264 | __u128 apdbkey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:268:9: error: unknown
type name '__u128'; did you mean '__u32'?
268 | __u128 apgakey;
| ^~~~~~ __u32
cc1: note: unrecognized command-line option
'-Wno-gnu-variable-sized-type-not-at-end' may have been intended
to silence earlier diagnostics make[1]: *** [Makefile.kvm:347:
/tmp/next/arm64_kselftest/kselftest/kvm/lib/userfaultfd_util.o] Error 1
In file included from /usr/include/aarch64-linux-gnu/bits/sigcontext.h:30,
from /usr/include/signal.h:301,
from irqfd_test.c:7:
/tmp/next/arm64_kselftest/usr/include/asm/sigcontext.h:81:9: error:
unknown type name '__u128'; did you mean '__u32'?
81 | __u128 vregs[32];
| ^~~~~~ __u32
In file included from /tmp/next/arm64_kselftest/usr/include/asm/kvm.h:37,
from /tmp/next/arm64_kselftest/usr/include/linux/kvm.h:16,
from include/kvm_util.h:14,
from irqfd_test.c:11:
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:96:9: error: unknown
type name '__u128'; did you mean '__u32'?
96 | __u128 vregs[32];
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:261:9: error: unknown
type name '__u128'; did you mean '__u32'?
261 | __u128 apiakey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:262:9: error: unknown
type name '__u128'; did you mean '__u32'?
262 | __u128 apibkey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:263:9: error: unknown
type name '__u128'; did you mean '__u32'?
263 | __u128 apdakey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:264:9: error: unknown
type name '__u128'; did you mean '__u32'?
264 | __u128 apdbkey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:268:9: error: unknown
type name '__u128'; did you mean '__u32'?
268 | __u128 apgakey;
| ^~~~~~ __u32
cc1: note: unrecognized command-line option
'-Wno-gnu-variable-sized-type-not-at-end' may have been intended
to silence earlier diagnostics make[1]: *** [Makefile.kvm:332:
/tmp/next/arm64_kselftest/kselftest/kvm/irqfd_test.o] Error 1 In file
included from /usr/include/aarch64-linux-gnu/bits/sigcontext.h:30,
from /usr/include/signal.h:301,
from include/test_util.h:12,
from kvm_binary_stats_test.c:15:
/tmp/next/arm64_kselftest/usr/include/asm/sigcontext.h:81:9: error:
unknown type name '__u128'; did you mean '__u32'?
81 | __u128 vregs[32];
| ^~~~~~ __u32
In file included from /tmp/next/arm64_kselftest/usr/include/asm/kvm.h:37,
from /tmp/next/arm64_kselftest/usr/include/linux/kvm.h:16,
from include/kvm_util.h:14,
from kvm_binary_stats_test.c:17:
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:96:9: error: unknown
type name '__u128'; did you mean '__u32'?
96 | __u128 vregs[32];
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:261:9: error: unknown
type name '__u128'; did you mean '__u32'?
261 | __u128 apiakey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:262:9: error: unknown
type name '__u128'; did you mean '__u32'?
262 | __u128 apibkey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:263:9: error: unknown
type name '__u128'; did you mean '__u32'?
263 | __u128 apdakey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:264:9: error: unknown
type name '__u128'; did you mean '__u32'?
264 | __u128 apdbkey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:268:9: error: unknown
type name '__u128'; did you mean '__u32'?
268 | __u128 apgakey;
| ^~~~~~ __u32
cc1: note: unrecognized command-line option
'-Wno-gnu-variable-sized-type-not-at-end' may have been intended
to silence earlier diagnostics make[1]: *** [Makefile.kvm:332:
/tmp/next/arm64_kselftest/kselftest/kvm/kvm_binary_stats_test.o] Error 1
In file included from /usr/include/aarch64-linux-gnu/bits/sigcontext.h:30,
from /usr/include/signal.h:301,
from arm64/host_sve.c:10:
/tmp/next/arm64_kselftest/usr/include/asm/sigcontext.h:81:9: error:
unknown type name '__u128'; did you mean '__u32'?
81 | __u128 vregs[32];
| ^~~~~~ __u32
In file included from /tmp/next/arm64_kselftest/usr/include/asm/kvm.h:37,
from arm64/host_sve.c:12:
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:96:9: error: unknown
type name '__u128'; did you mean '__u32'?
96 | __u128 vregs[32];
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:261:9: error: unknown
type name '__u128'; did you mean '__u32'?
261 | __u128 apiakey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:262:9: error: unknown
type name '__u128'; did you mean '__u32'?
262 | __u128 apibkey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:263:9: error: unknown
type name '__u128'; did you mean '__u32'?
263 | __u128 apdakey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:264:9: error: unknown
type name '__u128'; did you mean '__u32'?
264 | __u128 apdbkey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:268:9: error: unknown
type name '__u128'; did you mean '__u32'?
268 | __u128 apgakey;
| ^~~~~~ __u32
cc1: note: unrecognized command-line option
'-Wno-gnu-variable-sized-type-not-at-end' may have been intended
to silence earlier diagnostics make[1]: *** [Makefile.kvm:332:
/tmp/next/arm64_kselftest/kselftest/kvm/arm64/host_sve.o] Error 1 In
file included from /usr/include/aarch64-linux-gnu/bits/sigcontext.h:30,
from /usr/include/signal.h:301,
from include/test_util.h:12,
from include/kvm_util.h:8,
from include/guest_modes.h:5,
from lib/guest_modes.c:5:
/tmp/next/arm64_kselftest/usr/include/asm/sigcontext.h:81:9: error:
unknown type name '__u128'; did you mean '__u32'?
81 | __u128 vregs[32];
| ^~~~~~ __u32
In file included from /tmp/next/arm64_kselftest/usr/include/asm/kvm.h:37,
from /tmp/next/arm64_kselftest/usr/include/linux/kvm.h:16,
from include/kvm_util.h:14:
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:96:9: error: unknown
type name '__u128'; did you mean '__u32'?
96 | __u128 vregs[32];
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:261:9: error: unknown
type name '__u128'; did you mean '__u32'?
261 | __u128 apiakey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:262:9: error: unknown
type name '__u128'; did you mean '__u32'?
262 | __u128 apibkey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:263:9: error: unknown
type name '__u128'; did you mean '__u32'?
263 | __u128 apdakey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:264:9: error: unknown
type name '__u128'; did you mean '__u32'?
264 | __u128 apdbkey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:268:9: error: unknown
type name '__u128'; did you mean '__u32'?
268 | __u128 apgakey;
| ^~~~~~ __u32
cc1: note: unrecognized command-line option
'-Wno-gnu-variable-sized-type-not-at-end' may have been intended
to silence earlier diagnostics make[1]: *** [Makefile.kvm:347:
/tmp/next/arm64_kselftest/kselftest/kvm/lib/guest_modes.o] Error 1 In
file included from /usr/include/aarch64-linux-gnu/bits/sigcontext.h:30,
from /usr/include/signal.h:301,
from include/test_util.h:12,
from include/kvm_util.h:8,
from include/timer_test.h:11,
from arch_timer.c:28:
/tmp/next/arm64_kselftest/usr/include/asm/sigcontext.h:81:9: error:
unknown type name '__u128'; did you mean '__u32'?
81 | __u128 vregs[32];
| ^~~~~~ __u32
In file included from /tmp/next/arm64_kselftest/usr/include/asm/kvm.h:37,
from /tmp/next/arm64_kselftest/usr/include/linux/kvm.h:16,
from include/kvm_util.h:14:
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:96:9: error: unknown
type name '__u128'; did you mean '__u32'?
96 | __u128 vregs[32];
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:261:9: error: unknown
type name '__u128'; did you mean '__u32'?
261 | __u128 apiakey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:262:9: error: unknown
type name '__u128'; did you mean '__u32'?
262 | __u128 apibkey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:263:9: error: unknown
type name '__u128'; did you mean '__u32'?
263 | __u128 apdakey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:264:9: error: unknown
type name '__u128'; did you mean '__u32'?
264 | __u128 apdbkey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:268:9: error: unknown
type name '__u128'; did you mean '__u32'?
268 | __u128 apgakey;
| ^~~~~~ __u32
cc1: note: unrecognized command-line option
'-Wno-gnu-variable-sized-type-not-at-end' may have been intended
to silence earlier diagnostics make[1]: *** [Makefile.kvm:332:
/tmp/next/arm64_kselftest/kselftest/kvm/arch_timer.o] Error 1 In file
included from /usr/include/aarch64-linux-gnu/bits/sigcontext.h:30,
from /usr/include/signal.h:301,
from include/test_util.h:12,
from include/kvm_util.h:8,
from lib/arm64/gic.c:10:
/tmp/next/arm64_kselftest/usr/include/asm/sigcontext.h:81:9: error:
unknown type name '__u128'; did you mean '__u32'?
81 | __u128 vregs[32];
| ^~~~~~ __u32
In file included from /tmp/next/arm64_kselftest/usr/include/asm/kvm.h:37,
from /tmp/next/arm64_kselftest/usr/include/linux/kvm.h:16,
from include/kvm_util.h:14:
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:96:9: error: unknown
type name '__u128'; did you mean '__u32'?
96 | __u128 vregs[32];
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:261:9: error: unknown
type name '__u128'; did you mean '__u32'?
261 | __u128 apiakey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:262:9: error: unknown
type name '__u128'; did you mean '__u32'?
262 | __u128 apibkey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:263:9: error: unknown
type name '__u128'; did you mean '__u32'?
263 | __u128 apdakey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:264:9: error: unknown
type name '__u128'; did you mean '__u32'?
264 | __u128 apdbkey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:268:9: error: unknown
type name '__u128'; did you mean '__u32'?
268 | __u128 apgakey;
| ^~~~~~ __u32
cc1: note: unrecognized command-line option
'-Wno-gnu-variable-sized-type-not-at-end' may have been intended
to silence earlier diagnostics make[1]: *** [Makefile.kvm:347:
/tmp/next/arm64_kselftest/kselftest/kvm/lib/arm64/gic.o] Error 1 In file
included from /tmp/next/arm64_kselftest/usr/include/asm/kvm.h:37,
from /tmp/next/arm64_kselftest/usr/include/linux/kvm.h:16,
from lib/arm64/vgic.c:7:
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:96:9: error: unknown
type name '__u128'; did you mean '__u32'?
96 | __u128 vregs[32];
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:261:9: error: unknown
type name '__u128'; did you mean '__u32'?
261 | __u128 apiakey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:262:9: error: unknown
type name '__u128'; did you mean '__u32'?
262 | __u128 apibkey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:263:9: error: unknown
type name '__u128'; did you mean '__u32'?
263 | __u128 apdakey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:264:9: error: unknown
type name '__u128'; did you mean '__u32'?
264 | __u128 apdbkey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:268:9: error: unknown
type name '__u128'; did you mean '__u32'?
268 | __u128 apgakey;
| ^~~~~~ __u32
In file included from /usr/include/aarch64-linux-gnu/bits/sigcontext.h:30,
from /usr/include/signal.h:301,
from include/test_util.h:12,
from include/kvm_util.h:8,
from lib/arm64/vgic.c:13:
/tmp/next/arm64_kselftest/usr/include/asm/sigcontext.h:81:9: error:
unknown type name '__u128'; did you mean '__u32'?
81 | __u128 vregs[32];
| ^~~~~~ __u32
cc1: note: unrecognized command-line option
'-Wno-gnu-variable-sized-type-not-at-end' may have been intended
to silence earlier diagnostics make[1]: *** [Makefile.kvm:347:
/tmp/next/arm64_kselftest/kselftest/kvm/lib/arm64/vgic.o] Error 1 In
file included from /usr/include/aarch64-linux-gnu/bits/sigcontext.h:30,
from /usr/include/signal.h:301,
from include/test_util.h:12,
from include/kvm_util.h:8,
from dirty_log_perf_test.c:17:
/tmp/next/arm64_kselftest/usr/include/asm/sigcontext.h:81:9: error:
unknown type name '__u128'; did you mean '__u32'?
81 | __u128 vregs[32];
| ^~~~~~ __u32
In file included from /tmp/next/arm64_kselftest/usr/include/asm/kvm.h:37,
from /tmp/next/arm64_kselftest/usr/include/linux/kvm.h:16,
from include/kvm_util.h:14:
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:96:9: error: unknown
type name '__u128'; did you mean '__u32'?
96 | __u128 vregs[32];
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:261:9: error: unknown
type name '__u128'; did you mean '__u32'?
261 | __u128 apiakey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:262:9: error: unknown
type name '__u128'; did you mean '__u32'?
262 | __u128 apibkey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:263:9: error: unknown
type name '__u128'; did you mean '__u32'?
263 | __u128 apdakey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:264:9: error: unknown
type name '__u128'; did you mean '__u32'?
264 | __u128 apdbkey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:268:9: error: unknown
type name '__u128'; did you mean '__u32'?
268 | __u128 apgakey;
| ^~~~~~ __u32
cc1: note: unrecognized command-line option
'-Wno-gnu-variable-sized-type-not-at-end' may have been intended
to silence earlier diagnostics make[1]: *** [Makefile.kvm:332:
/tmp/next/arm64_kselftest/kselftest/kvm/dirty_log_perf_test.o] Error 1
In file included from /tmp/next/arm64_kselftest/usr/include/asm/kvm.h:37,
from /tmp/next/arm64_kselftest/usr/include/linux/kvm.h:16,
from lib/arm64/gic_v3_its.c:7:
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:96:9: error: unknown
type name '__u128'; did you mean '__u32'?
96 | __u128 vregs[32];
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:261:9: error: unknown
type name '__u128'; did you mean '__u32'?
261 | __u128 apiakey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:262:9: error: unknown
type name '__u128'; did you mean '__u32'?
262 | __u128 apibkey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:263:9: error: unknown
type name '__u128'; did you mean '__u32'?
263 | __u128 apdakey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:264:9: error: unknown
type name '__u128'; did you mean '__u32'?
264 | __u128 apdbkey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:268:9: error: unknown
type name '__u128'; did you mean '__u32'?
268 | __u128 apgakey;
| ^~~~~~ __u32
In file included from /usr/include/aarch64-linux-gnu/bits/sigcontext.h:30,
from /usr/include/signal.h:301,
from include/test_util.h:12,
from include/kvm_util.h:8,
from lib/arm64/gic_v3_its.c:12:
/tmp/next/arm64_kselftest/usr/include/asm/sigcontext.h:81:9: error:
unknown type name '__u128'; did you mean '__u32'?
81 | __u128 vregs[32];
| ^~~~~~ __u32
cc1: note: unrecognized command-line option
'-Wno-gnu-variable-sized-type-not-at-end' may have been intended
to silence earlier diagnostics make[1]: *** [Makefile.kvm:347:
/tmp/next/arm64_kselftest/kselftest/kvm/lib/arm64/gic_v3_its.o] Error 1
In file included from /usr/include/aarch64-linux-gnu/bits/sigcontext.h:30,
from /usr/include/signal.h:301,
from include/test_util.h:12,
from include/kvm_util.h:8,
from lib/memstress.c:8:
/tmp/next/arm64_kselftest/usr/include/asm/sigcontext.h:81:9: error:
unknown type name '__u128'; did you mean '__u32'?
81 | __u128 vregs[32];
| ^~~~~~ __u32
In file included from /tmp/next/arm64_kselftest/usr/include/asm/kvm.h:37,
from /tmp/next/arm64_kselftest/usr/include/linux/kvm.h:16,
from include/kvm_util.h:14:
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:96:9: error: unknown
type name '__u128'; did you mean '__u32'?
96 | __u128 vregs[32];
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:261:9: error: unknown
type name '__u128'; did you mean '__u32'?
261 | __u128 apiakey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:262:9: error: unknown
type name '__u128'; did you mean '__u32'?
262 | __u128 apibkey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:263:9: error: unknown
type name '__u128'; did you mean '__u32'?
263 | __u128 apdakey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:264:9: error: unknown
type name '__u128'; did you mean '__u32'?
264 | __u128 apdbkey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:268:9: error: unknown
type name '__u128'; did you mean '__u32'?
268 | __u128 apgakey;
| ^~~~~~ __u32
cc1: note: unrecognized command-line option
'-Wno-gnu-variable-sized-type-not-at-end' may have been intended
to silence earlier diagnostics make[1]: *** [Makefile.kvm:347:
/tmp/next/arm64_kselftest/kselftest/kvm/lib/memstress.o] Error 1 In file
included from /usr/include/aarch64-linux-gnu/bits/sigcontext.h:30,
from /usr/include/signal.h:301,
from include/test_util.h:12,
from include/kvm_util.h:8,
from lib/arm64/gic_v3.c:8:
/tmp/next/arm64_kselftest/usr/include/asm/sigcontext.h:81:9: error:
unknown type name '__u128'; did you mean '__u32'?
81 | __u128 vregs[32];
| ^~~~~~ __u32
In file included from /tmp/next/arm64_kselftest/usr/include/asm/kvm.h:37,
from /tmp/next/arm64_kselftest/usr/include/linux/kvm.h:16,
from include/kvm_util.h:14:
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:96:9: error: unknown
type name '__u128'; did you mean '__u32'?
96 | __u128 vregs[32];
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:261:9: error: unknown
type name '__u128'; did you mean '__u32'?
261 | __u128 apiakey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:262:9: error: unknown
type name '__u128'; did you mean '__u32'?
262 | __u128 apibkey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:263:9: error: unknown
type name '__u128'; did you mean '__u32'?
263 | __u128 apdakey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:264:9: error: unknown
type name '__u128'; did you mean '__u32'?
264 | __u128 apdbkey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:268:9: error: unknown
type name '__u128'; did you mean '__u32'?
268 | __u128 apgakey;
| ^~~~~~ __u32
cc1: note: unrecognized command-line option
'-Wno-gnu-variable-sized-type-not-at-end' may have been intended
to silence earlier diagnostics make[1]: *** [Makefile.kvm:347:
/tmp/next/arm64_kselftest/kselftest/kvm/lib/arm64/gic_v3.o] Error 1 In
file included from /usr/include/aarch64-linux-gnu/bits/sigcontext.h:30,
from /usr/include/signal.h:301,
from include/test_util.h:12,
from guest_print_test.c:13:
/tmp/next/arm64_kselftest/usr/include/asm/sigcontext.h:81:9: error:
unknown type name '__u128'; did you mean '__u32'?
81 | __u128 vregs[32];
| ^~~~~~ __u32
In file included from /tmp/next/arm64_kselftest/usr/include/asm/kvm.h:37,
from /tmp/next/arm64_kselftest/usr/include/linux/kvm.h:16,
from include/kvm_util.h:14,
from guest_print_test.c:14:
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:96:9: error: unknown
type name '__u128'; did you mean '__u32'?
96 | __u128 vregs[32];
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:261:9: error: unknown
type name '__u128'; did you mean '__u32'?
261 | __u128 apiakey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:262:9: error: unknown
type name '__u128'; did you mean '__u32'?
262 | __u128 apibkey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:263:9: error: unknown
type name '__u128'; did you mean '__u32'?
263 | __u128 apdakey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:264:9: error: unknown
type name '__u128'; did you mean '__u32'?
264 | __u128 apdbkey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:268:9: error: unknown
type name '__u128'; did you mean '__u32'?
268 | __u128 apgakey;
| ^~~~~~ __u32
cc1: note: unrecognized command-line option
'-Wno-gnu-variable-sized-type-not-at-end' may have been intended
to silence earlier diagnostics make[1]: *** [Makefile.kvm:332:
/tmp/next/arm64_kselftest/kselftest/kvm/guest_print_test.o] Error 1 In
file included from /usr/include/aarch64-linux-gnu/bits/sigcontext.h:30,
from /usr/include/signal.h:301,
from set_memory_region_test.c:6:
/tmp/next/arm64_kselftest/usr/include/asm/sigcontext.h:81:9: error:
unknown type name '__u128'; did you mean '__u32'?
81 | __u128 vregs[32];
| ^~~~~~ __u32
In file included from /tmp/next/arm64_kselftest/usr/include/asm/kvm.h:37,
from /tmp/next/arm64_kselftest/usr/include/linux/kvm.h:16,
from include/kvm_util.h:14,
from set_memory_region_test.c:16:
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:96:9: error: unknown
type name '__u128'; did you mean '__u32'?
96 | __u128 vregs[32];
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:261:9: error: unknown
type name '__u128'; did you mean '__u32'?
261 | __u128 apiakey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:262:9: error: unknown
type name '__u128'; did you mean '__u32'?
262 | __u128 apibkey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:263:9: error: unknown
type name '__u128'; did you mean '__u32'?
263 | __u128 apdakey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:264:9: error: unknown
type name '__u128'; did you mean '__u32'?
264 | __u128 apdbkey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:268:9: error: unknown
type name '__u128'; did you mean '__u32'?
268 | __u128 apgakey;
| ^~~~~~ __u32
cc1: note: unrecognized command-line option
'-Wno-gnu-variable-sized-type-not-at-end' may have been intended
to silence earlier diagnostics make[1]: *** [Makefile.kvm:332:
/tmp/next/arm64_kselftest/kselftest/kvm/set_memory_region_test.o] Error 1
In file included from /tmp/next/arm64_kselftest/usr/include/asm/kvm.h:37,
from arm64/hypercalls.c:13:
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:96:9: error: unknown
type name '__u128'; did you mean '__u32'?
96 | __u128 vregs[32];
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:261:9: error: unknown
type name '__u128'; did you mean '__u32'?
261 | __u128 apiakey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:262:9: error: unknown
type name '__u128'; did you mean '__u32'?
262 | __u128 apibkey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:263:9: error: unknown
type name '__u128'; did you mean '__u32'?
263 | __u128 apdakey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:264:9: error: unknown
type name '__u128'; did you mean '__u32'?
264 | __u128 apdbkey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:268:9: error: unknown
type name '__u128'; did you mean '__u32'?
268 | __u128 apgakey;
| ^~~~~~ __u32
In file included from /usr/include/aarch64-linux-gnu/bits/sigcontext.h:30,
from /usr/include/signal.h:301,
from include/test_util.h:12,
from include/kvm_util.h:8,
from arm64/hypercalls.c:14:
/tmp/next/arm64_kselftest/usr/include/asm/sigcontext.h:81:9: error:
unknown type name '__u128'; did you mean '__u32'?
81 | __u128 vregs[32];
| ^~~~~~ __u32
cc1: note: unrecognized command-line option
'-Wno-gnu-variable-sized-type-not-at-end' may have been intended
to silence earlier diagnostics make[1]: *** [Makefile.kvm:332:
/tmp/next/arm64_kselftest/kselftest/kvm/arm64/hypercalls.o] Error 1 In
file included from /usr/include/aarch64-linux-gnu/bits/sigcontext.h:30,
from /usr/include/signal.h:301,
from include/test_util.h:12,
from kvm_page_table_test.c:17:
/tmp/next/arm64_kselftest/usr/include/asm/sigcontext.h:81:9: error:
unknown type name '__u128'; did you mean '__u32'?
81 | __u128 vregs[32];
| ^~~~~~ __u32
In file included from /tmp/next/arm64_kselftest/usr/include/asm/kvm.h:37,
from /tmp/next/arm64_kselftest/usr/include/linux/kvm.h:16,
from include/kvm_util.h:14,
from kvm_page_table_test.c:18:
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:96:9: error: unknown
type name '__u128'; did you mean '__u32'?
96 | __u128 vregs[32];
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:261:9: error: unknown
type name '__u128'; did you mean '__u32'?
261 | __u128 apiakey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:262:9: error: unknown
type name '__u128'; did you mean '__u32'?
262 | __u128 apibkey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:263:9: error: unknown
type name '__u128'; did you mean '__u32'?
263 | __u128 apdakey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:264:9: error: unknown
type name '__u128'; did you mean '__u32'?
264 | __u128 apdbkey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:268:9: error: unknown
type name '__u128'; did you mean '__u32'?
268 | __u128 apgakey;
| ^~~~~~ __u32
cc1: note: unrecognized command-line option
'-Wno-gnu-variable-sized-type-not-at-end' may have been intended
to silence earlier diagnostics make[1]: *** [Makefile.kvm:332:
/tmp/next/arm64_kselftest/kselftest/kvm/kvm_page_table_test.o] Error 1
In file included from /tmp/next/arm64_kselftest/usr/include/asm/kvm.h:37,
from arm64/kvm-uuid.c:7:
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:96:9: error: unknown
type name '__u128'; did you mean '__u32'?
96 | __u128 vregs[32];
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:261:9: error: unknown
type name '__u128'; did you mean '__u32'?
261 | __u128 apiakey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:262:9: error: unknown
type name '__u128'; did you mean '__u32'?
262 | __u128 apibkey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:263:9: error: unknown
type name '__u128'; did you mean '__u32'?
263 | __u128 apdakey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:264:9: error: unknown
type name '__u128'; did you mean '__u32'?
264 | __u128 apdbkey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:268:9: error: unknown
type name '__u128'; did you mean '__u32'?
268 | __u128 apgakey;
| ^~~~~~ __u32
In file included from /usr/include/aarch64-linux-gnu/bits/sigcontext.h:30,
from /usr/include/signal.h:301,
from include/test_util.h:12,
from include/kvm_util.h:8,
from arm64/kvm-uuid.c:8:
/tmp/next/arm64_kselftest/usr/include/asm/sigcontext.h:81:9: error:
unknown type name '__u128'; did you mean '__u32'?
81 | __u128 vregs[32];
| ^~~~~~ __u32
cc1: note: unrecognized command-line option
'-Wno-gnu-variable-sized-type-not-at-end' may have been intended
to silence earlier diagnostics make[1]: *** [Makefile.kvm:332:
/tmp/next/arm64_kselftest/kselftest/kvm/arm64/kvm-uuid.o] Error 1 In
file included from /usr/include/aarch64-linux-gnu/bits/sigcontext.h:30,
from /usr/include/signal.h:301,
from include/test_util.h:12,
from include/kvm_util.h:8,
from arm64/vcpu_width_config.c:12:
/tmp/next/arm64_kselftest/usr/include/asm/sigcontext.h:81:9: error:
unknown type name '__u128'; did you mean '__u32'?
81 | __u128 vregs[32];
| ^~~~~~ __u32
In file included from /tmp/next/arm64_kselftest/usr/include/asm/kvm.h:37,
from /tmp/next/arm64_kselftest/usr/include/linux/kvm.h:16,
from include/kvm_util.h:14:
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:96:9: error: unknown
type name '__u128'; did you mean '__u32'?
96 | __u128 vregs[32];
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:261:9: error: unknown
type name '__u128'; did you mean '__u32'?
261 | __u128 apiakey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:262:9: error: unknown
type name '__u128'; did you mean '__u32'?
262 | __u128 apibkey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:263:9: error: unknown
type name '__u128'; did you mean '__u32'?
263 | __u128 apdakey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:264:9: error: unknown
type name '__u128'; did you mean '__u32'?
264 | __u128 apdbkey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:268:9: error: unknown
type name '__u128'; did you mean '__u32'?
268 | __u128 apgakey;
| ^~~~~~ __u32
cc1: note: unrecognized command-line option
'-Wno-gnu-variable-sized-type-not-at-end' may have been intended
to silence earlier diagnostics make[1]: *** [Makefile.kvm:332:
/tmp/next/arm64_kselftest/kselftest/kvm/arm64/vcpu_width_config.o] Error 1
In file included from /usr/include/aarch64-linux-gnu/bits/sigcontext.h:30,
from /usr/include/signal.h:301,
from include/test_util.h:12,
from include/kvm_syscalls.h:15,
from guest_memfd_test.c:20:
/tmp/next/arm64_kselftest/usr/include/asm/sigcontext.h:81:9: error:
unknown type name '__u128'; did you mean '__u32'?
81 | __u128 vregs[32];
| ^~~~~~ __u32
In file included from /tmp/next/arm64_kselftest/usr/include/asm/kvm.h:37,
from /tmp/next/arm64_kselftest/usr/include/linux/kvm.h:16,
from include/kvm_util.h:14,
from guest_memfd_test.c:21:
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:96:9: error: unknown
type name '__u128'; did you mean '__u32'?
96 | __u128 vregs[32];
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:261:9: error: unknown
type name '__u128'; did you mean '__u32'?
261 | __u128 apiakey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:262:9: error: unknown
type name '__u128'; did you mean '__u32'?
262 | __u128 apibkey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:263:9: error: unknown
type name '__u128'; did you mean '__u32'?
263 | __u128 apdakey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:264:9: error: unknown
type name '__u128'; did you mean '__u32'?
264 | __u128 apdbkey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:268:9: error: unknown
type name '__u128'; did you mean '__u32'?
268 | __u128 apgakey;
| ^~~~~~ __u32
cc1: note: unrecognized command-line option
'-Wno-gnu-variable-sized-type-not-at-end' may have been intended
to silence earlier diagnostics make[1]: *** [Makefile.kvm:332:
/tmp/next/arm64_kselftest/kselftest/kvm/guest_memfd_test.o] Error 1 In
file included from /usr/include/aarch64-linux-gnu/bits/sigcontext.h:30,
from /usr/include/signal.h:301,
from include/test_util.h:12,
from include/kvm_util.h:8,
from include/memstress.h:13,
from memslot_modification_stress_test.c:21:
/tmp/next/arm64_kselftest/usr/include/asm/sigcontext.h:81:9: error:
unknown type name '__u128'; did you mean '__u32'?
81 | __u128 vregs[32];
| ^~~~~~ __u32
In file included from /tmp/next/arm64_kselftest/usr/include/asm/kvm.h:37,
from /tmp/next/arm64_kselftest/usr/include/linux/kvm.h:16,
from include/kvm_util.h:14:
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:96:9: error: unknown
type name '__u128'; did you mean '__u32'?
96 | __u128 vregs[32];
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:261:9: error: unknown
type name '__u128'; did you mean '__u32'?
261 | __u128 apiakey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:262:9: error: unknown
type name '__u128'; did you mean '__u32'?
262 | __u128 apibkey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:263:9: error: unknown
type name '__u128'; did you mean '__u32'?
263 | __u128 apdakey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:264:9: error: unknown
type name '__u128'; did you mean '__u32'?
264 | __u128 apdbkey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:268:9: error: unknown
type name '__u128'; did you mean '__u32'?
268 | __u128 apgakey;
| ^~~~~~ __u32
cc1: note: unrecognized command-line option
'-Wno-gnu-variable-sized-type-not-at-end' may have been intended
to silence earlier diagnostics make[1]: *** [Makefile.kvm:332:
/tmp/next/arm64_kselftest/kselftest/kvm/memslot_modification_stress_test.o]
Error 1 In file included from
/usr/include/aarch64-linux-gnu/bits/sigcontext.h:30,
from /usr/include/signal.h:301,
from include/test_util.h:12,
from include/kvm_util.h:8,
from include/arm64/processor.h:10,
from arm64/smccc_filter.c:17:
/tmp/next/arm64_kselftest/usr/include/asm/sigcontext.h:81:9: error:
unknown type name '__u128'; did you mean '__u32'?
81 | __u128 vregs[32];
| ^~~~~~ __u32
In file included from /tmp/next/arm64_kselftest/usr/include/asm/kvm.h:37,
from /tmp/next/arm64_kselftest/usr/include/linux/kvm.h:16,
from include/kvm_util.h:14:
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:96:9: error: unknown
type name '__u128'; did you mean '__u32'?
96 | __u128 vregs[32];
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:261:9: error: unknown
type name '__u128'; did you mean '__u32'?
261 | __u128 apiakey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:262:9: error: unknown
type name '__u128'; did you mean '__u32'?
262 | __u128 apibkey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:263:9: error: unknown
type name '__u128'; did you mean '__u32'?
263 | __u128 apdakey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:264:9: error: unknown
type name '__u128'; did you mean '__u32'?
264 | __u128 apdbkey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:268:9: error: unknown
type name '__u128'; did you mean '__u32'?
268 | __u128 apgakey;
| ^~~~~~ __u32
cc1: note: unrecognized command-line option
'-Wno-gnu-variable-sized-type-not-at-end' may have been intended
to silence earlier diagnostics make[1]: *** [Makefile.kvm:332:
/tmp/next/arm64_kselftest/kselftest/kvm/arm64/smccc_filter.o] Error 1
In file included from /usr/include/aarch64-linux-gnu/bits/sigcontext.h:30,
from /usr/include/signal.h:301,
from dirty_log_test.c:12:
/tmp/next/arm64_kselftest/usr/include/asm/sigcontext.h:81:9: error:
unknown type name '__u128'; did you mean '__u32'?
81 | __u128 vregs[32];
| ^~~~~~ __u32
In file included from /tmp/next/arm64_kselftest/usr/include/asm/kvm.h:37,
from /tmp/next/arm64_kselftest/usr/include/linux/kvm.h:16,
from include/kvm_util.h:14,
from dirty_log_test.c:19:
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:96:9: error: unknown
type name '__u128'; did you mean '__u32'?
96 | __u128 vregs[32];
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:261:9: error: unknown
type name '__u128'; did you mean '__u32'?
261 | __u128 apiakey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:262:9: error: unknown
type name '__u128'; did you mean '__u32'?
262 | __u128 apibkey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:263:9: error: unknown
type name '__u128'; did you mean '__u32'?
263 | __u128 apdakey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:264:9: error: unknown
type name '__u128'; did you mean '__u32'?
264 | __u128 apdbkey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:268:9: error: unknown
type name '__u128'; did you mean '__u32'?
268 | __u128 apgakey;
| ^~~~~~ __u32
cc1: note: unrecognized command-line option
'-Wno-gnu-variable-sized-type-not-at-end' may have been intended
to silence earlier diagnostics make[1]: *** [Makefile.kvm:332:
/tmp/next/arm64_kselftest/kselftest/kvm/dirty_log_test.o] Error 1 In
file included from /usr/include/aarch64-linux-gnu/bits/sigcontext.h:30,
from /usr/include/signal.h:301,
from arm64/sea_to_user.c:17:
/tmp/next/arm64_kselftest/usr/include/asm/sigcontext.h:81:9: error:
unknown type name '__u128'; did you mean '__u32'?
81 | __u128 vregs[32];
| ^~~~~~ __u32
In file included from /tmp/next/arm64_kselftest/usr/include/asm/kvm.h:37,
from /tmp/next/arm64_kselftest/usr/include/linux/kvm.h:16,
from include/kvm_util.h:14,
from arm64/sea_to_user.c:23:
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:96:9: error: unknown
type name '__u128'; did you mean '__u32'?
96 | __u128 vregs[32];
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:261:9: error: unknown
type name '__u128'; did you mean '__u32'?
261 | __u128 apiakey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:262:9: error: unknown
type name '__u128'; did you mean '__u32'?
262 | __u128 apibkey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:263:9: error: unknown
type name '__u128'; did you mean '__u32'?
263 | __u128 apdakey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:264:9: error: unknown
type name '__u128'; did you mean '__u32'?
264 | __u128 apdbkey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:268:9: error: unknown
type name '__u128'; did you mean '__u32'?
268 | __u128 apgakey;
| ^~~~~~ __u32
cc1: note: unrecognized command-line option
'-Wno-gnu-variable-sized-type-not-at-end' may have been intended
to silence earlier diagnostics make[1]: *** [Makefile.kvm:332:
/tmp/next/arm64_kselftest/kselftest/kvm/arm64/sea_to_user.o] Error 1 In
file included from /usr/include/aarch64-linux-gnu/bits/sigcontext.h:30,
from /usr/include/signal.h:301,
from include/test_util.h:12,
from memslot_perf_test.c:24:
/tmp/next/arm64_kselftest/usr/include/asm/sigcontext.h:81:9: error:
unknown type name '__u128'; did you mean '__u32'?
81 | __u128 vregs[32];
| ^~~~~~ __u32
In file included from /tmp/next/arm64_kselftest/usr/include/asm/kvm.h:37,
from /tmp/next/arm64_kselftest/usr/include/linux/kvm.h:16,
from include/kvm_util.h:14,
from memslot_perf_test.c:26:
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:96:9: error: unknown
type name '__u128'; did you mean '__u32'?
96 | __u128 vregs[32];
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:261:9: error: unknown
type name '__u128'; did you mean '__u32'?
261 | __u128 apiakey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:262:9: error: unknown
type name '__u128'; did you mean '__u32'?
262 | __u128 apibkey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:263:9: error: unknown
type name '__u128'; did you mean '__u32'?
263 | __u128 apdakey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:264:9: error: unknown
type name '__u128'; did you mean '__u32'?
264 | __u128 apdbkey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:268:9: error: unknown
type name '__u128'; did you mean '__u32'?
268 | __u128 apgakey;
| ^~~~~~ __u32
cc1: note: unrecognized command-line option
'-Wno-gnu-variable-sized-type-not-at-end' may have been intended
to silence earlier diagnostics make[1]: *** [Makefile.kvm:332:
/tmp/next/arm64_kselftest/kselftest/kvm/memslot_perf_test.o] Error 1 In
file included from /usr/include/aarch64-linux-gnu/bits/sigcontext.h:30,
from /usr/include/signal.h:301,
from include/test_util.h:12,
from include/kvm_util.h:8,
from arm64/vgic_lpi_stress.c:13:
/tmp/next/arm64_kselftest/usr/include/asm/sigcontext.h:81:9: error:
unknown type name '__u128'; did you mean '__u32'?
81 | __u128 vregs[32];
| ^~~~~~ __u32
In file included from /tmp/next/arm64_kselftest/usr/include/asm/kvm.h:37,
from /tmp/next/arm64_kselftest/usr/include/linux/kvm.h:16,
from include/kvm_util.h:14:
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:96:9: error: unknown
type name '__u128'; did you mean '__u32'?
96 | __u128 vregs[32];
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:261:9: error: unknown
type name '__u128'; did you mean '__u32'?
261 | __u128 apiakey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:262:9: error: unknown
type name '__u128'; did you mean '__u32'?
262 | __u128 apibkey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:263:9: error: unknown
type name '__u128'; did you mean '__u32'?
263 | __u128 apdakey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:264:9: error: unknown
type name '__u128'; did you mean '__u32'?
264 | __u128 apdbkey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:268:9: error: unknown
type name '__u128'; did you mean '__u32'?
268 | __u128 apgakey;
| ^~~~~~ __u32
cc1: note: unrecognized command-line option
'-Wno-gnu-variable-sized-type-not-at-end' may have been intended
to silence earlier diagnostics make[1]: *** [Makefile.kvm:332:
/tmp/next/arm64_kselftest/kselftest/kvm/arm64/vgic_lpi_stress.o] Error 1
In file included from /usr/include/aarch64-linux-gnu/bits/sigcontext.h:30,
from /usr/include/signal.h:301,
from include/test_util.h:12,
from include/kvm_util.h:8,
from arm64/aarch32_id_regs.c:13:
/tmp/next/arm64_kselftest/usr/include/asm/sigcontext.h:81:9: error:
unknown type name '__u128'; did you mean '__u32'?
81 | __u128 vregs[32];
| ^~~~~~ __u32
In file included from /tmp/next/arm64_kselftest/usr/include/asm/kvm.h:37,
from /tmp/next/arm64_kselftest/usr/include/linux/kvm.h:16,
from include/kvm_util.h:14:
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:96:9: error: unknown
type name '__u128'; did you mean '__u32'?
96 | __u128 vregs[32];
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:261:9: error: unknown
type name '__u128'; did you mean '__u32'?
261 | __u128 apiakey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:262:9: error: unknown
type name '__u128'; did you mean '__u32'?
262 | __u128 apibkey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:263:9: error: unknown
type name '__u128'; did you mean '__u32'?
263 | __u128 apdakey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:264:9: error: unknown
type name '__u128'; did you mean '__u32'?
264 | __u128 apdbkey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:268:9: error: unknown
type name '__u128'; did you mean '__u32'?
268 | __u128 apgakey;
| ^~~~~~ __u32
cc1: note: unrecognized command-line option
'-Wno-gnu-variable-sized-type-not-at-end' may have been intended
to silence earlier diagnostics make[1]: *** [Makefile.kvm:332:
/tmp/next/arm64_kselftest/kselftest/kvm/arm64/aarch32_id_regs.o] Error 1
In file included from /usr/include/aarch64-linux-gnu/bits/sigcontext.h:30,
from /usr/include/signal.h:301,
from include/test_util.h:12,
from arm64/idreg-idst.c:8:
/tmp/next/arm64_kselftest/usr/include/asm/sigcontext.h:81:9: error:
unknown type name '__u128'; did you mean '__u32'?
81 | __u128 vregs[32];
| ^~~~~~ __u32
In file included from /tmp/next/arm64_kselftest/usr/include/asm/kvm.h:37,
from /tmp/next/arm64_kselftest/usr/include/linux/kvm.h:16,
from include/kvm_util.h:14,
from arm64/idreg-idst.c:9:
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:96:9: error: unknown
type name '__u128'; did you mean '__u32'?
96 | __u128 vregs[32];
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:261:9: error: unknown
type name '__u128'; did you mean '__u32'?
261 | __u128 apiakey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:262:9: error: unknown
type name '__u128'; did you mean '__u32'?
262 | __u128 apibkey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:263:9: error: unknown
type name '__u128'; did you mean '__u32'?
263 | __u128 apdakey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:264:9: error: unknown
type name '__u128'; did you mean '__u32'?
264 | __u128 apdbkey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:268:9: error: unknown
type name '__u128'; did you mean '__u32'?
268 | __u128 apgakey;
| ^~~~~~ __u32
cc1: note: unrecognized command-line option
'-Wno-gnu-variable-sized-type-not-at-end' may have been intended
to silence earlier diagnostics make[1]: *** [Makefile.kvm:332:
/tmp/next/arm64_kselftest/kselftest/kvm/arm64/idreg-idst.o] Error 1 In
file included from /usr/include/aarch64-linux-gnu/bits/sigcontext.h:30,
from /usr/include/signal.h:301,
from include/test_util.h:12,
from include/kvm_util.h:8,
from include/arm64/processor.h:10,
from include/arm64/arch_timer.h:9,
from arm64/arch_timer_edge_cases.c:21:
/tmp/next/arm64_kselftest/usr/include/asm/sigcontext.h:81:9: error:
unknown type name '__u128'; did you mean '__u32'?
81 | __u128 vregs[32];
| ^~~~~~ __u32
In file included from /tmp/next/arm64_kselftest/usr/include/asm/kvm.h:37,
from /tmp/next/arm64_kselftest/usr/include/linux/kvm.h:16,
from include/kvm_util.h:14:
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:96:9: error: unknown
type name '__u128'; did you mean '__u32'?
96 | __u128 vregs[32];
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:261:9: error: unknown
type name '__u128'; did you mean '__u32'?
261 | __u128 apiakey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:262:9: error: unknown
type name '__u128'; did you mean '__u32'?
262 | __u128 apibkey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:263:9: error: unknown
type name '__u128'; did you mean '__u32'?
263 | __u128 apdakey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:264:9: error: unknown
type name '__u128'; did you mean '__u32'?
264 | __u128 apdbkey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:268:9: error: unknown
type name '__u128'; did you mean '__u32'?
268 | __u128 apgakey;
| ^~~~~~ __u32
cc1: note: unrecognized command-line option
'-Wno-gnu-variable-sized-type-not-at-end' may have been intended
to silence earlier diagnostics make[1]: *** [Makefile.kvm:332:
/tmp/next/arm64_kselftest/kselftest/kvm/arm64/arch_timer_edge_cases.o]
Error 1 In file included from
/usr/include/aarch64-linux-gnu/bits/sigcontext.h:30,
from /usr/include/signal.h:301,
from coalesced_io_test.c:2:
/tmp/next/arm64_kselftest/usr/include/asm/sigcontext.h:81:9: error:
unknown type name '__u128'; did you mean '__u32'?
81 | __u128 vregs[32];
| ^~~~~~ __u32
In file included from /tmp/next/arm64_kselftest/usr/include/asm/kvm.h:37,
from /tmp/next/arm64_kselftest/usr/include/linux/kvm.h:16,
from include/kvm_util.h:14,
from coalesced_io_test.c:10:
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:96:9: error: unknown
type name '__u128'; did you mean '__u32'?
96 | __u128 vregs[32];
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:261:9: error: unknown
type name '__u128'; did you mean '__u32'?
261 | __u128 apiakey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:262:9: error: unknown
type name '__u128'; did you mean '__u32'?
262 | __u128 apibkey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:263:9: error: unknown
type name '__u128'; did you mean '__u32'?
263 | __u128 apdakey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:264:9: error: unknown
type name '__u128'; did you mean '__u32'?
264 | __u128 apdbkey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:268:9: error: unknown
type name '__u128'; did you mean '__u32'?
268 | __u128 apgakey;
| ^~~~~~ __u32
cc1: note: unrecognized command-line option
'-Wno-gnu-variable-sized-type-not-at-end' may have been intended
to silence earlier diagnostics make[1]: *** [Makefile.kvm:332:
/tmp/next/arm64_kselftest/kselftest/kvm/coalesced_io_test.o] Error 1 In
file included from /usr/include/aarch64-linux-gnu/bits/sigcontext.h:30,
from /usr/include/signal.h:301,
from include/test_util.h:12,
from include/kvm_util.h:8,
from arm64/hello_el2.c:7:
/tmp/next/arm64_kselftest/usr/include/asm/sigcontext.h:81:9: error:
unknown type name '__u128'; did you mean '__u32'?
81 | __u128 vregs[32];
| ^~~~~~ __u32
In file included from /tmp/next/arm64_kselftest/usr/include/asm/kvm.h:37,
from /tmp/next/arm64_kselftest/usr/include/linux/kvm.h:16,
from include/kvm_util.h:14:
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:96:9: error: unknown
type name '__u128'; did you mean '__u32'?
96 | __u128 vregs[32];
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:261:9: error: unknown
type name '__u128'; did you mean '__u32'?
261 | __u128 apiakey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:262:9: error: unknown
type name '__u128'; did you mean '__u32'?
262 | __u128 apibkey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:263:9: error: unknown
type name '__u128'; did you mean '__u32'?
263 | __u128 apdakey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:264:9: error: unknown
type name '__u128'; did you mean '__u32'?
264 | __u128 apdbkey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:268:9: error: unknown
type name '__u128'; did you mean '__u32'?
268 | __u128 apgakey;
| ^~~~~~ __u32
cc1: note: unrecognized command-line option
'-Wno-gnu-variable-sized-type-not-at-end' may have been intended
to silence earlier diagnostics make[1]: *** [Makefile.kvm:332:
/tmp/next/arm64_kselftest/kselftest/kvm/arm64/hello_el2.o] Error 1 In
file included from /usr/include/aarch64-linux-gnu/bits/sigcontext.h:30,
from /usr/include/signal.h:301,
from include/test_util.h:12,
from include/kvm_util.h:8,
from include/arm64/processor.h:10,
from include/arm64/arch_timer.h:9,
from arm64/arch_timer.c:8:
/tmp/next/arm64_kselftest/usr/include/asm/sigcontext.h:81:9: error:
unknown type name '__u128'; did you mean '__u32'?
81 | __u128 vregs[32];
| ^~~~~~ __u32
In file included from /tmp/next/arm64_kselftest/usr/include/asm/kvm.h:37,
from /tmp/next/arm64_kselftest/usr/include/linux/kvm.h:16,
from include/kvm_util.h:14:
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:96:9: error: unknown
type name '__u128'; did you mean '__u32'?
96 | __u128 vregs[32];
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:261:9: error: unknown
type name '__u128'; did you mean '__u32'?
261 | __u128 apiakey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:262:9: error: unknown
type name '__u128'; did you mean '__u32'?
262 | __u128 apibkey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:263:9: error: unknown
type name '__u128'; did you mean '__u32'?
263 | __u128 apdakey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:264:9: error: unknown
type name '__u128'; did you mean '__u32'?
264 | __u128 apdbkey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:268:9: error: unknown
type name '__u128'; did you mean '__u32'?
268 | __u128 apgakey;
| ^~~~~~ __u32
cc1: note: unrecognized command-line option
'-Wno-gnu-variable-sized-type-not-at-end' may have been intended
to silence earlier diagnostics make[1]: *** [Makefile.kvm:337:
/tmp/next/arm64_kselftest/kselftest/kvm/arm64/arch_timer.o] Error 1 In
file included from /tmp/next/arm64_kselftest/usr/include/asm/kvm.h:37,
from arm64/vgic_irq.c:10:
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:96:9: error: unknown
type name '__u128'; did you mean '__u32'?
96 | __u128 vregs[32];
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:261:9: error: unknown
type name '__u128'; did you mean '__u32'?
261 | __u128 apiakey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:262:9: error: unknown
type name '__u128'; did you mean '__u32'?
262 | __u128 apibkey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:263:9: error: unknown
type name '__u128'; did you mean '__u32'?
263 | __u128 apdakey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:264:9: error: unknown
type name '__u128'; did you mean '__u32'?
264 | __u128 apdbkey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:268:9: error: unknown
type name '__u128'; did you mean '__u32'?
268 | __u128 apgakey;
| ^~~~~~ __u32
In file included from /usr/include/aarch64-linux-gnu/bits/sigcontext.h:30,
from /usr/include/signal.h:301,
from include/test_util.h:12,
from include/kvm_util.h:8,
from include/arm64/processor.h:10,
from arm64/vgic_irq.c:15:
/tmp/next/arm64_kselftest/usr/include/asm/sigcontext.h:81:9: error:
unknown type name '__u128'; did you mean '__u32'?
81 | __u128 vregs[32];
| ^~~~~~ __u32
cc1: note: unrecognized command-line option
'-Wno-gnu-variable-sized-type-not-at-end' may have been intended
to silence earlier diagnostics make[1]: *** [Makefile.kvm:332:
/tmp/next/arm64_kselftest/kselftest/kvm/arm64/vgic_irq.o] Error 1 In
file included from /usr/include/aarch64-linux-gnu/bits/sigcontext.h:30,
from /usr/include/signal.h:301,
from /usr/include/aarch64-linux-gnu/sys/wait.h:36,
from get-reg-list.c:26:
/tmp/next/arm64_kselftest/usr/include/asm/sigcontext.h:81:9: error:
unknown type name '__u128'; did you mean '__u32'?
81 | __u128 vregs[32];
| ^~~~~~ __u32
In file included from /tmp/next/arm64_kselftest/usr/include/asm/kvm.h:37,
from /tmp/next/arm64_kselftest/usr/include/linux/kvm.h:16,
from include/kvm_util.h:14,
from get-reg-list.c:27:
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:96:9: error: unknown
type name '__u128'; did you mean '__u32'?
96 | __u128 vregs[32];
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:261:9: error: unknown
type name '__u128'; did you mean '__u32'?
261 | __u128 apiakey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:262:9: error: unknown
type name '__u128'; did you mean '__u32'?
262 | __u128 apibkey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:263:9: error: unknown
type name '__u128'; did you mean '__u32'?
263 | __u128 apdakey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:264:9: error: unknown
type name '__u128'; did you mean '__u32'?
264 | __u128 apdbkey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:268:9: error: unknown
type name '__u128'; did you mean '__u32'?
268 | __u128 apgakey;
| ^~~~~~ __u32
cc1: note: unrecognized command-line option
'-Wno-gnu-variable-sized-type-not-at-end' may have been intended
to silence earlier diagnostics make[1]: *** [Makefile.kvm:332:
/tmp/next/arm64_kselftest/kselftest/kvm/get-reg-list.o] Error 1 In file
included from /usr/include/aarch64-linux-gnu/bits/sigcontext.h:30,
from /usr/include/signal.h:301,
from include/test_util.h:12,
from include/kvm_syscalls.h:15,
from access_tracking_perf_test.c:47:
/tmp/next/arm64_kselftest/usr/include/asm/sigcontext.h:81:9: error:
unknown type name '__u128'; did you mean '__u32'?
81 | __u128 vregs[32];
| ^~~~~~ __u32
In file included from /tmp/next/arm64_kselftest/usr/include/asm/kvm.h:37,
from /tmp/next/arm64_kselftest/usr/include/linux/kvm.h:16,
from include/kvm_util.h:14,
from access_tracking_perf_test.c:48:
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:96:9: error: unknown
type name '__u128'; did you mean '__u32'?
96 | __u128 vregs[32];
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:261:9: error: unknown
type name '__u128'; did you mean '__u32'?
261 | __u128 apiakey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:262:9: error: unknown
type name '__u128'; did you mean '__u32'?
262 | __u128 apibkey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:263:9: error: unknown
type name '__u128'; did you mean '__u32'?
263 | __u128 apdakey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:264:9: error: unknown
type name '__u128'; did you mean '__u32'?
264 | __u128 apdbkey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:268:9: error: unknown
type name '__u128'; did you mean '__u32'?
268 | __u128 apgakey;
| ^~~~~~ __u32
cc1: note: unrecognized command-line option
'-Wno-gnu-variable-sized-type-not-at-end' may have been intended
to silence earlier diagnostics make[1]: *** [Makefile.kvm:332:
/tmp/next/arm64_kselftest/kselftest/kvm/access_tracking_perf_test.o]
Error 1 In file included from
/tmp/next/arm64_kselftest/usr/include/asm/kvm.h:37,
from steal_time.c:12:
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:96:9: error: unknown
type name '__u128'; did you mean '__u32'?
96 | __u128 vregs[32];
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:261:9: error: unknown
type name '__u128'; did you mean '__u32'?
261 | __u128 apiakey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:262:9: error: unknown
type name '__u128'; did you mean '__u32'?
262 | __u128 apibkey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:263:9: error: unknown
type name '__u128'; did you mean '__u32'?
263 | __u128 apdakey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:264:9: error: unknown
type name '__u128'; did you mean '__u32'?
264 | __u128 apdbkey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:268:9: error: unknown
type name '__u128'; did you mean '__u32'?
268 | __u128 apgakey;
| ^~~~~~ __u32
In file included from /usr/include/aarch64-linux-gnu/bits/sigcontext.h:30,
from /usr/include/signal.h:301,
from include/test_util.h:12,
from steal_time.c:19:
/tmp/next/arm64_kselftest/usr/include/asm/sigcontext.h:81:9: error:
unknown type name '__u128'; did you mean '__u32'?
81 | __u128 vregs[32];
| ^~~~~~ __u32
cc1: note: unrecognized command-line option
'-Wno-gnu-variable-sized-type-not-at-end' may have been intended
to silence earlier diagnostics make[1]: *** [Makefile.kvm:332:
/tmp/next/arm64_kselftest/kselftest/kvm/steal_time.o] Error 1 In file
included from /usr/include/aarch64-linux-gnu/bits/sigcontext.h:30,
from /usr/include/signal.h:301,
from include/test_util.h:12,
from include/kvm_util.h:8,
from include/arm64/processor.h:10,
from arm64/external_aborts.c:7:
/tmp/next/arm64_kselftest/usr/include/asm/sigcontext.h:81:9: error:
unknown type name '__u128'; did you mean '__u32'?
81 | __u128 vregs[32];
| ^~~~~~ __u32
In file included from /tmp/next/arm64_kselftest/usr/include/asm/kvm.h:37,
from /tmp/next/arm64_kselftest/usr/include/linux/kvm.h:16,
from include/kvm_util.h:14:
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:96:9: error: unknown
type name '__u128'; did you mean '__u32'?
96 | __u128 vregs[32];
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:261:9: error: unknown
type name '__u128'; did you mean '__u32'?
261 | __u128 apiakey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:262:9: error: unknown
type name '__u128'; did you mean '__u32'?
262 | __u128 apibkey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:263:9: error: unknown
type name '__u128'; did you mean '__u32'?
263 | __u128 apdakey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:264:9: error: unknown
type name '__u128'; did you mean '__u32'?
264 | __u128 apdbkey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:268:9: error: unknown
type name '__u128'; did you mean '__u32'?
268 | __u128 apgakey;
| ^~~~~~ __u32
cc1: note: unrecognized command-line option
'-Wno-gnu-variable-sized-type-not-at-end' may have been intended
to silence earlier diagnostics make[1]: *** [Makefile.kvm:332:
/tmp/next/arm64_kselftest/kselftest/kvm/arm64/external_aborts.o] Error 1
In file included from /usr/include/aarch64-linux-gnu/bits/sigcontext.h:30,
from /usr/include/signal.h:301,
from include/test_util.h:12,
from include/kvm_util.h:8,
from arm64/psci_test.c:18:
/tmp/next/arm64_kselftest/usr/include/asm/sigcontext.h:81:9: error:
unknown type name '__u128'; did you mean '__u32'?
81 | __u128 vregs[32];
| ^~~~~~ __u32
In file included from /tmp/next/arm64_kselftest/usr/include/asm/kvm.h:37,
from /tmp/next/arm64_kselftest/usr/include/linux/kvm.h:16,
from include/kvm_util.h:14:
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:96:9: error: unknown
type name '__u128'; did you mean '__u32'?
96 | __u128 vregs[32];
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:261:9: error: unknown
type name '__u128'; did you mean '__u32'?
261 | __u128 apiakey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:262:9: error: unknown
type name '__u128'; did you mean '__u32'?
262 | __u128 apibkey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:263:9: error: unknown
type name '__u128'; did you mean '__u32'?
263 | __u128 apdakey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:264:9: error: unknown
type name '__u128'; did you mean '__u32'?
264 | __u128 apdbkey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:268:9: error: unknown
type name '__u128'; did you mean '__u32'?
268 | __u128 apgakey;
| ^~~~~~ __u32
cc1: note: unrecognized command-line option
'-Wno-gnu-variable-sized-type-not-at-end' may have been intended
to silence earlier diagnostics make[1]: *** [Makefile.kvm:332:
/tmp/next/arm64_kselftest/kselftest/kvm/arm64/psci_test.o] Error 1 In
file included from /tmp/next/arm64_kselftest/usr/include/asm/kvm.h:37,
from arm64/vgic_v5.c:5:
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:96:9: error: unknown
type name '__u128'; did you mean '__u32'?
96 | __u128 vregs[32];
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:261:9: error: unknown
type name '__u128'; did you mean '__u32'?
261 | __u128 apiakey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:262:9: error: unknown
type name '__u128'; did you mean '__u32'?
262 | __u128 apibkey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:263:9: error: unknown
type name '__u128'; did you mean '__u32'?
263 | __u128 apdakey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:264:9: error: unknown
type name '__u128'; did you mean '__u32'?
264 | __u128 apdbkey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:268:9: error: unknown
type name '__u128'; did you mean '__u32'?
268 | __u128 apgakey;
| ^~~~~~ __u32
In file included from /usr/include/aarch64-linux-gnu/bits/sigcontext.h:30,
from /usr/include/signal.h:301,
from include/test_util.h:12,
from include/kvm_util.h:8,
from include/arm64/processor.h:10,
from include/arm64/gic_v5.h:11,
from arm64/vgic_v5.c:8:
/tmp/next/arm64_kselftest/usr/include/asm/sigcontext.h:81:9: error:
unknown type name '__u128'; did you mean '__u32'?
81 | __u128 vregs[32];
| ^~~~~~ __u32
cc1: note: unrecognized command-line option
'-Wno-gnu-variable-sized-type-not-at-end' may have been intended
to silence earlier diagnostics make[1]: *** [Makefile.kvm:332:
/tmp/next/arm64_kselftest/kselftest/kvm/arm64/vgic_v5.o] Error 1 In file
included from /usr/include/aarch64-linux-gnu/bits/sigcontext.h:30,
from /usr/include/signal.h:301,
from mmu_stress_test.c:7:
/tmp/next/arm64_kselftest/usr/include/asm/sigcontext.h:81:9: error:
unknown type name '__u128'; did you mean '__u32'?
81 | __u128 vregs[32];
| ^~~~~~ __u32
In file included from /tmp/next/arm64_kselftest/usr/include/asm/kvm.h:37,
from /tmp/next/arm64_kselftest/usr/include/linux/kvm.h:16,
from include/kvm_util.h:14,
from mmu_stress_test.c:14:
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:96:9: error: unknown
type name '__u128'; did you mean '__u32'?
96 | __u128 vregs[32];
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:261:9: error: unknown
type name '__u128'; did you mean '__u32'?
261 | __u128 apiakey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:262:9: error: unknown
type name '__u128'; did you mean '__u32'?
262 | __u128 apibkey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:263:9: error: unknown
type name '__u128'; did you mean '__u32'?
263 | __u128 apdakey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:264:9: error: unknown
type name '__u128'; did you mean '__u32'?
264 | __u128 apdbkey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:268:9: error: unknown
type name '__u128'; did you mean '__u32'?
268 | __u128 apgakey;
| ^~~~~~ __u32
cc1: note: unrecognized command-line option
'-Wno-gnu-variable-sized-type-not-at-end' may have been intended
to silence earlier diagnostics make[1]: *** [Makefile.kvm:332:
/tmp/next/arm64_kselftest/kselftest/kvm/mmu_stress_test.o] Error 1 In
file included from /tmp/next/arm64_kselftest/usr/include/asm/kvm.h:37,
from arm64/vgic_init.c:9:
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:96:9: error: unknown
type name '__u128'; did you mean '__u32'?
96 | __u128 vregs[32];
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:261:9: error: unknown
type name '__u128'; did you mean '__u32'?
261 | __u128 apiakey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:262:9: error: unknown
type name '__u128'; did you mean '__u32'?
262 | __u128 apibkey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:263:9: error: unknown
type name '__u128'; did you mean '__u32'?
263 | __u128 apdakey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:264:9: error: unknown
type name '__u128'; did you mean '__u32'?
264 | __u128 apdbkey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:268:9: error: unknown
type name '__u128'; did you mean '__u32'?
268 | __u128 apgakey;
| ^~~~~~ __u32
In file included from /usr/include/aarch64-linux-gnu/bits/sigcontext.h:30,
from /usr/include/signal.h:301,
from include/test_util.h:12,
from arm64/vgic_init.c:14:
/tmp/next/arm64_kselftest/usr/include/asm/sigcontext.h:81:9: error:
unknown type name '__u128'; did you mean '__u32'?
81 | __u128 vregs[32];
| ^~~~~~ __u32
cc1: note: unrecognized command-line option
'-Wno-gnu-variable-sized-type-not-at-end' may have been intended
to silence earlier diagnostics make[1]: *** [Makefile.kvm:332:
/tmp/next/arm64_kselftest/kselftest/kvm/arm64/vgic_init.o] Error 1 In
file included from /usr/include/aarch64-linux-gnu/bits/sigcontext.h:30,
from /usr/include/signal.h:301,
from include/test_util.h:12,
from arm64/debug-exceptions.c:2:
/tmp/next/arm64_kselftest/usr/include/asm/sigcontext.h:81:9: error:
unknown type name '__u128'; did you mean '__u32'?
81 | __u128 vregs[32];
| ^~~~~~ __u32
In file included from /tmp/next/arm64_kselftest/usr/include/asm/kvm.h:37,
from /tmp/next/arm64_kselftest/usr/include/linux/kvm.h:16,
from include/kvm_util.h:14,
from arm64/debug-exceptions.c:3:
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:96:9: error: unknown
type name '__u128'; did you mean '__u32'?
96 | __u128 vregs[32];
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:261:9: error: unknown
type name '__u128'; did you mean '__u32'?
261 | __u128 apiakey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:262:9: error: unknown
type name '__u128'; did you mean '__u32'?
262 | __u128 apibkey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:263:9: error: unknown
type name '__u128'; did you mean '__u32'?
263 | __u128 apdakey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:264:9: error: unknown
type name '__u128'; did you mean '__u32'?
264 | __u128 apdbkey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:268:9: error: unknown
type name '__u128'; did you mean '__u32'?
268 | __u128 apgakey;
| ^~~~~~ __u32
cc1: note: unrecognized command-line option
'-Wno-gnu-variable-sized-type-not-at-end' may have been intended
to silence earlier diagnostics make[1]: *** [Makefile.kvm:332:
/tmp/next/arm64_kselftest/kselftest/kvm/arm64/debug-exceptions.o] Error 1
In file included from /usr/include/aarch64-linux-gnu/bits/sigcontext.h:30,
from /usr/include/signal.h:301,
from include/test_util.h:12,
from arm64/page_fault_test.c:12:
/tmp/next/arm64_kselftest/usr/include/asm/sigcontext.h:81:9: error:
unknown type name '__u128'; did you mean '__u32'?
81 | __u128 vregs[32];
| ^~~~~~ __u32
In file included from /tmp/next/arm64_kselftest/usr/include/asm/kvm.h:37,
from /tmp/next/arm64_kselftest/usr/include/linux/kvm.h:16,
from include/kvm_util.h:14,
from arm64/page_fault_test.c:13:
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:96:9: error: unknown
type name '__u128'; did you mean '__u32'?
96 | __u128 vregs[32];
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:261:9: error: unknown
type name '__u128'; did you mean '__u32'?
261 | __u128 apiakey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:262:9: error: unknown
type name '__u128'; did you mean '__u32'?
262 | __u128 apibkey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:263:9: error: unknown
type name '__u128'; did you mean '__u32'?
263 | __u128 apdakey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:264:9: error: unknown
type name '__u128'; did you mean '__u32'?
264 | __u128 apdbkey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:268:9: error: unknown
type name '__u128'; did you mean '__u32'?
268 | __u128 apgakey;
| ^~~~~~ __u32
cc1: note: unrecognized command-line option
'-Wno-gnu-variable-sized-type-not-at-end' may have been intended
to silence earlier diagnostics make[1]: *** [Makefile.kvm:332:
/tmp/next/arm64_kselftest/kselftest/kvm/arm64/page_fault_test.o] Error 1
In file included from /usr/include/aarch64-linux-gnu/bits/sigcontext.h:30,
from /usr/include/signal.h:301,
from include/test_util.h:12,
from include/kvm_util.h:8,
from arm64/vpmu_counter_access.c:15:
/tmp/next/arm64_kselftest/usr/include/asm/sigcontext.h:81:9: error:
unknown type name '__u128'; did you mean '__u32'?
81 | __u128 vregs[32];
| ^~~~~~ __u32
In file included from /tmp/next/arm64_kselftest/usr/include/asm/kvm.h:37,
from /tmp/next/arm64_kselftest/usr/include/linux/kvm.h:16,
from include/kvm_util.h:14:
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:96:9: error: unknown
type name '__u128'; did you mean '__u32'?
96 | __u128 vregs[32];
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:261:9: error: unknown
type name '__u128'; did you mean '__u32'?
261 | __u128 apiakey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:262:9: error: unknown
type name '__u128'; did you mean '__u32'?
262 | __u128 apibkey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:263:9: error: unknown
type name '__u128'; did you mean '__u32'?
263 | __u128 apdakey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:264:9: error: unknown
type name '__u128'; did you mean '__u32'?
264 | __u128 apdbkey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:268:9: error: unknown
type name '__u128'; did you mean '__u32'?
268 | __u128 apgakey;
| ^~~~~~ __u32
cc1: note: unrecognized command-line option
'-Wno-gnu-variable-sized-type-not-at-end' may have been intended
to silence earlier diagnostics make[1]: *** [Makefile.kvm:332:
/tmp/next/arm64_kselftest/kselftest/kvm/arm64/vpmu_counter_access.o]
Error 1 In file included from
/usr/include/aarch64-linux-gnu/bits/sigcontext.h:30,
from /usr/include/signal.h:301,
from include/test_util.h:12,
from include/kvm_util.h:8,
from include/guest_modes.h:5,
from lib/arm64/processor.c:11:
/tmp/next/arm64_kselftest/usr/include/asm/sigcontext.h:81:9: error:
unknown type name '__u128'; did you mean '__u32'?
81 | __u128 vregs[32];
| ^~~~~~ __u32
In file included from /tmp/next/arm64_kselftest/usr/include/asm/kvm.h:37,
from /tmp/next/arm64_kselftest/usr/include/linux/kvm.h:16,
from include/kvm_util.h:14:
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:96:9: error: unknown
type name '__u128'; did you mean '__u32'?
96 | __u128 vregs[32];
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:261:9: error: unknown
type name '__u128'; did you mean '__u32'?
261 | __u128 apiakey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:262:9: error: unknown
type name '__u128'; did you mean '__u32'?
262 | __u128 apibkey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:263:9: error: unknown
type name '__u128'; did you mean '__u32'?
263 | __u128 apdakey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:264:9: error: unknown
type name '__u128'; did you mean '__u32'?
264 | __u128 apdbkey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:268:9: error: unknown
type name '__u128'; did you mean '__u32'?
268 | __u128 apgakey;
| ^~~~~~ __u32
cc1: note: unrecognized command-line option
'-Wno-gnu-variable-sized-type-not-at-end' may have been intended
to silence earlier diagnostics make[1]: *** [Makefile.kvm:347:
/tmp/next/arm64_kselftest/kselftest/kvm/lib/arm64/processor.o] Error 1
In file included from /usr/include/aarch64-linux-gnu/bits/sigcontext.h:30,
from /usr/include/signal.h:301,
from include/test_util.h:12,
from lib/kvm_util.c:7:
/tmp/next/arm64_kselftest/usr/include/asm/sigcontext.h:81:9: error:
unknown type name '__u128'; did you mean '__u32'?
81 | __u128 vregs[32];
| ^~~~~~ __u32
In file included from /tmp/next/arm64_kselftest/usr/include/asm/kvm.h:37,
from /tmp/next/arm64_kselftest/usr/include/linux/kvm.h:16,
from include/kvm_util.h:14,
from lib/kvm_util.c:9:
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:96:9: error: unknown
type name '__u128'; did you mean '__u32'?
96 | __u128 vregs[32];
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:261:9: error: unknown
type name '__u128'; did you mean '__u32'?
261 | __u128 apiakey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:262:9: error: unknown
type name '__u128'; did you mean '__u32'?
262 | __u128 apibkey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:263:9: error: unknown
type name '__u128'; did you mean '__u32'?
263 | __u128 apdakey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:264:9: error: unknown
type name '__u128'; did you mean '__u32'?
264 | __u128 apdbkey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:268:9: error: unknown
type name '__u128'; did you mean '__u32'?
268 | __u128 apgakey;
| ^~~~~~ __u32
cc1: note: unrecognized command-line option
'-Wno-gnu-variable-sized-type-not-at-end' may have been intended
to silence earlier diagnostics make[1]: *** [Makefile.kvm:347:
/tmp/next/arm64_kselftest/kselftest/kvm/lib/kvm_util.o] Error 1 In file
included from /usr/include/aarch64-linux-gnu/bits/sigcontext.h:30,
from /usr/include/signal.h:301,
from ../rseq/rseq.c:27,
from rseq_test.c:8:
/tmp/next/arm64_kselftest/usr/include/asm/sigcontext.h:81:9: error:
unknown type name '__u128'; did you mean '__u32'?
81 | __u128 vregs[32];
| ^~~~~~ __u32
In file included from /tmp/next/arm64_kselftest/usr/include/asm/kvm.h:37,
from /tmp/next/arm64_kselftest/usr/include/linux/kvm.h:16,
from include/kvm_util.h:14,
from rseq_test.c:27:
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:96:9: error: unknown
type name '__u128'; did you mean '__u32'?
96 | __u128 vregs[32];
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:261:9: error: unknown
type name '__u128'; did you mean '__u32'?
261 | __u128 apiakey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:262:9: error: unknown
type name '__u128'; did you mean '__u32'?
262 | __u128 apibkey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:263:9: error: unknown
type name '__u128'; did you mean '__u32'?
263 | __u128 apdakey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:264:9: error: unknown
type name '__u128'; did you mean '__u32'?
264 | __u128 apdbkey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:268:9: error: unknown
type name '__u128'; did you mean '__u32'?
268 | __u128 apgakey;
| ^~~~~~ __u32
cc1: note: unrecognized command-line option
'-Wno-gnu-variable-sized-type-not-at-end' may have been intended
to silence earlier diagnostics make[1]: *** [Makefile.kvm:332:
/tmp/next/arm64_kselftest/kselftest/kvm/rseq_test.o] Error 1 In file
included from /usr/include/aarch64-linux-gnu/bits/sigcontext.h:30,
from /usr/include/signal.h:301,
from include/test_util.h:12,
from include/kvm_util.h:8,
from arm64/get-reg-list.c:14:
/tmp/next/arm64_kselftest/usr/include/asm/sigcontext.h:81:9: error:
unknown type name '__u128'; did you mean '__u32'?
81 | __u128 vregs[32];
| ^~~~~~ __u32
In file included from /tmp/next/arm64_kselftest/usr/include/asm/kvm.h:37,
from /tmp/next/arm64_kselftest/usr/include/linux/kvm.h:16,
from include/kvm_util.h:14:
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:96:9: error: unknown
type name '__u128'; did you mean '__u32'?
96 | __u128 vregs[32];
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:261:9: error: unknown
type name '__u128'; did you mean '__u32'?
261 | __u128 apiakey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:262:9: error: unknown
type name '__u128'; did you mean '__u32'?
262 | __u128 apibkey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:263:9: error: unknown
type name '__u128'; did you mean '__u32'?
263 | __u128 apdakey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:264:9: error: unknown
type name '__u128'; did you mean '__u32'?
264 | __u128 apdbkey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:268:9: error: unknown
type name '__u128'; did you mean '__u32'?
268 | __u128 apgakey;
| ^~~~~~ __u32
cc1: note: unrecognized command-line option
'-Wno-gnu-variable-sized-type-not-at-end' may have been intended
to silence earlier diagnostics make[1]: *** [Makefile.kvm:337:
/tmp/next/arm64_kselftest/kselftest/kvm/arm64/get-reg-list.o] Error 1
In file included from /usr/include/aarch64-linux-gnu/bits/sigcontext.h:30,
from /usr/include/signal.h:301,
from include/test_util.h:12,
from arm64/no-vgic.c:8:
/tmp/next/arm64_kselftest/usr/include/asm/sigcontext.h:81:9: error:
unknown type name '__u128'; did you mean '__u32'?
81 | __u128 vregs[32];
| ^~~~~~ __u32
In file included from /tmp/next/arm64_kselftest/usr/include/asm/kvm.h:37,
from /tmp/next/arm64_kselftest/usr/include/linux/kvm.h:16,
from include/kvm_util.h:14,
from arm64/no-vgic.c:9:
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:96:9: error: unknown
type name '__u128'; did you mean '__u32'?
96 | __u128 vregs[32];
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:261:9: error: unknown
type name '__u128'; did you mean '__u32'?
261 | __u128 apiakey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:262:9: error: unknown
type name '__u128'; did you mean '__u32'?
262 | __u128 apibkey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:263:9: error: unknown
type name '__u128'; did you mean '__u32'?
263 | __u128 apdakey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:264:9: error: unknown
type name '__u128'; did you mean '__u32'?
264 | __u128 apdbkey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:268:9: error: unknown
type name '__u128'; did you mean '__u32'?
268 | __u128 apgakey;
| ^~~~~~ __u32
cc1: note: unrecognized command-line option
'-Wno-gnu-variable-sized-type-not-at-end' may have been intended
to silence earlier diagnostics make[1]: *** [Makefile.kvm:332:
/tmp/next/arm64_kselftest/kselftest/kvm/arm64/no-vgic.o] Error 1 In file
included from /usr/include/aarch64-linux-gnu/bits/sigcontext.h:30,
from /usr/include/signal.h:301,
from include/test_util.h:12,
from include/kvm_util.h:8,
from arm64/at.c:5:
/tmp/next/arm64_kselftest/usr/include/asm/sigcontext.h:81:9: error:
unknown type name '__u128'; did you mean '__u32'?
81 | __u128 vregs[32];
| ^~~~~~ __u32
In file included from /tmp/next/arm64_kselftest/usr/include/asm/kvm.h:37,
from /tmp/next/arm64_kselftest/usr/include/linux/kvm.h:16,
from include/kvm_util.h:14:
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:96:9: error: unknown
type name '__u128'; did you mean '__u32'?
96 | __u128 vregs[32];
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:261:9: error: unknown
type name '__u128'; did you mean '__u32'?
261 | __u128 apiakey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:262:9: error: unknown
type name '__u128'; did you mean '__u32'?
262 | __u128 apibkey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:263:9: error: unknown
type name '__u128'; did you mean '__u32'?
263 | __u128 apdakey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:264:9: error: unknown
type name '__u128'; did you mean '__u32'?
264 | __u128 apdbkey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:268:9: error: unknown
type name '__u128'; did you mean '__u32'?
268 | __u128 apgakey;
| ^~~~~~ __u32
cc1: note: unrecognized command-line option
'-Wno-gnu-variable-sized-type-not-at-end' may have been intended
to silence earlier diagnostics make[1]: *** [Makefile.kvm:332:
/tmp/next/arm64_kselftest/kselftest/kvm/arm64/at.o] Error 1 In file
included from /usr/include/aarch64-linux-gnu/bits/sigcontext.h:30,
from /usr/include/signal.h:301,
from include/test_util.h:12,
from include/kvm_util.h:8,
from arm64/set_id_regs.c:13:
/tmp/next/arm64_kselftest/usr/include/asm/sigcontext.h:81:9: error:
unknown type name '__u128'; did you mean '__u32'?
81 | __u128 vregs[32];
| ^~~~~~ __u32
In file included from /tmp/next/arm64_kselftest/usr/include/asm/kvm.h:37,
from /tmp/next/arm64_kselftest/usr/include/linux/kvm.h:16,
from include/kvm_util.h:14:
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:96:9: error: unknown
type name '__u128'; did you mean '__u32'?
96 | __u128 vregs[32];
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:261:9: error: unknown
type name '__u128'; did you mean '__u32'?
261 | __u128 apiakey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:262:9: error: unknown
type name '__u128'; did you mean '__u32'?
262 | __u128 apibkey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:263:9: error: unknown
type name '__u128'; did you mean '__u32'?
263 | __u128 apdakey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:264:9: error: unknown
type name '__u128'; did you mean '__u32'?
264 | __u128 apdbkey;
| ^~~~~~ __u32
/tmp/next/arm64_kselftest/usr/include/asm/ptrace.h:268:9: error: unknown
type name '__u128'; did you mean '__u32'?
268 | __u128 apgakey;
| ^~~~~~ __u32
Caused by commit
9d6306113f921 (arm64: uapi: Use __u128 instead of __uint128_t in UAPI headers)
I have used the tree from next-20260623 instead.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
^ permalink raw reply
* [STATUS] next/master - 4e5dfb7c84012007c3c7061126491bbc92d71bf1
From: KernelCI bot @ 2026-06-24 2:30 UTC (permalink / raw)
To: kernelci-results; +Cc: linux-next
Hello,
Status summary for next/master
Dashboard:
https://d.kernelci.org/c/next/master/4e5dfb7c84012007c3c7061126491bbc92d71bf1/
giturl: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
branch: master
commit hash: 4e5dfb7c84012007c3c7061126491bbc92d71bf1
origin: maestro
test start time: 2026-06-23 13:09:43.541000+00:00
Builds: 66 ✅ 2 ❌ 0 ⚠️
Boots: 136 ✅ 4 ❌ 0 ⚠️
Tests: 25709 ✅ 5004 ❌ 3637 ⚠️
### POSSIBLE REGRESSIONS
Hardware: dell-latitude-3445-7520c-skyrim
> Config: x86_64_defconfig+lab-setup+x86-board+kselftest
- Architecture/compiler: x86_64/gcc-14
- kselftest.cpufreq.suspend
last run: https://d.kernelci.org/test/maestro:6a3a991c6de4dcc0f43409b0
history: > ✅ > ✅ > ✅ > ✅ > ❌
- kselftest.cpufreq.suspend.cpufreq_main_sh
last run: https://d.kernelci.org/test/maestro:6a3a9ab66de4dcc0f4343521
history: > ✅ > ✅ > ✅ > ✅ > ❌
Hardware: mt8183-kukui-jacuzzi-juniper-sku16
> Config: defconfig+lab-setup+arm64-chromebook+CONFIG_MODULE_COMPRESS=n+CONFIG_MODULE_COMPRESS_NONE=y
- Architecture/compiler: arm64/gcc-14
- kselftest.dt.dt_test_unprobed_devices_sh_soc_dma-controller0_14001000
last run: https://d.kernelci.org/test/maestro:6a3a8fca6de4dcc0f433c604
history: > ✅ > ✅ > ✅ > ✅ > ❌
- kselftest.dt.dt_test_unprobed_devices_sh_soc_i2c_11008000_anx7625_58_aux-bus_panel
last run: https://d.kernelci.org/test/maestro:6a3a8fca6de4dcc0f433c5f8
history: > ✅ > ✅ > ✅ > ✅ > ❌
- kselftest.dt.dt_test_unprobed_devices_sh_soc_ovl_14008000
last run: https://d.kernelci.org/test/maestro:6a3a8fca6de4dcc0f433c5dc
history: > ✅ > ✅ > ✅ > ✅ > ❌
- kselftest.dt.dt_test_unprobed_devices_sh_soc_ovl_14009000
last run: https://d.kernelci.org/test/maestro:6a3a8fca6de4dcc0f433c5db
history: > ✅ > ✅ > ✅ > ✅ > ❌
- kselftest.dt.dt_test_unprobed_devices_sh_soc_ovl_1400a000
last run: https://d.kernelci.org/test/maestro:6a3a8fca6de4dcc0f433c5da
history: > ✅ > ✅ > ✅ > ✅ > ❌
- kselftest.dt.dt_test_unprobed_devices_sh_soc_rdma_1400b000
last run: https://d.kernelci.org/test/maestro:6a3a8fca6de4dcc0f433c5cf
history: > ✅ > ✅ > ✅ > ✅ > ❌
- kselftest.dt.dt_test_unprobed_devices_sh_soc_rdma_1400c000
last run: https://d.kernelci.org/test/maestro:6a3a8fca6de4dcc0f433c5ce
history: > ✅ > ✅ > ✅ > ✅ > ❌
Hardware: mt8195-cherry-tomato-r2
> Config: defconfig+lab-setup+arm64-chromebook+CONFIG_MODULE_COMPRESS=n+CONFIG_MODULE_COMPRESS_NONE=y
- Architecture/compiler: arm64/gcc-14
- kselftest.dt.dt_test_unprobed_devices_sh_mt8195-sound
last run: https://d.kernelci.org/test/maestro:6a3a90396de4dcc0f433d4a1
history: > ✅ > ✅ > ✅ > ❌
- kselftest.dt.dt_test_unprobed_devices_sh_soc_dma-controller_1c104000
last run: https://d.kernelci.org/test/maestro:6a3a90396de4dcc0f433d43e
history: > ✅ > ✅ > ✅ > ❌
- kselftest.dt.dt_test_unprobed_devices_sh_soc_dma-controller_1c105000
last run: https://d.kernelci.org/test/maestro:6a3a90396de4dcc0f433d43d
history: > ✅ > ✅ > ✅ > ❌
- kselftest.dt.dt_test_unprobed_devices_sh_soc_dma-controller_1c106000
last run: https://d.kernelci.org/test/maestro:6a3a90396de4dcc0f433d43c
history: > ✅ > ✅ > ✅ > ❌
- kselftest.dt.dt_test_unprobed_devices_sh_soc_dma-controller_1c107000
last run: https://d.kernelci.org/test/maestro:6a3a90396de4dcc0f433d43b
history: > ✅ > ✅ > ✅ > ❌
- kselftest.dt.dt_test_unprobed_devices_sh_soc_dma-controller_1c108000
last run: https://d.kernelci.org/test/maestro:6a3a90396de4dcc0f433d43a
history: > ✅ > ✅ > ✅ > ❌
- kselftest.dt.dt_test_unprobed_devices_sh_soc_dma-controller_1c109000
last run: https://d.kernelci.org/test/maestro:6a3a90396de4dcc0f433d439
history: > ✅ > ✅ > ✅ > ❌
- kselftest.dt.dt_test_unprobed_devices_sh_soc_dma-controller_1c10a000
last run: https://d.kernelci.org/test/maestro:6a3a90396de4dcc0f433d438
history: > ✅ > ✅ > ✅ > ❌
- kselftest.dt.dt_test_unprobed_devices_sh_soc_dma-controller_1c10b000
last run: https://d.kernelci.org/test/maestro:6a3a90396de4dcc0f433d437
history: > ✅ > ✅ > ✅ > ❌
- kselftest.dt.dt_test_unprobed_devices_sh_soc_dp-intf_1c015000
last run: https://d.kernelci.org/test/maestro:6a3a90396de4dcc0f433d436
history: > ✅ > ✅ > ✅ > ❌
- kselftest.dt.dt_test_unprobed_devices_sh_soc_dp-intf_1c113000
last run: https://d.kernelci.org/test/maestro:6a3a90396de4dcc0f433d435
history: > ✅ > ✅ > ✅ > ❌
- kselftest.dt.dt_test_unprobed_devices_sh_soc_hdr-engine_1c114000
last run: https://d.kernelci.org/test/maestro:6a3a90396de4dcc0f433d42c
history: > ✅ > ✅ > ✅ > ❌
- kselftest.dt.dt_test_unprobed_devices_sh_soc_jpeg-decoder_1a040000
last run: https://d.kernelci.org/test/maestro:6a3a90396de4dcc0f433d41b
history: > ✅ > ✅ > ✅ > ❌
- kselftest.dt.dt_test_unprobed_devices_sh_soc_jpeg-decoder_1a040000_jpgdec_0_0
last run: https://d.kernelci.org/test/maestro:6a3a90396de4dcc0f433d41a
history: > ✅ > ✅ > ✅ > ❌
- kselftest.dt.dt_test_unprobed_devices_sh_soc_jpeg-decoder_1a040000_jpgdec_0_10000
last run: https://d.kernelci.org/test/maestro:6a3a90396de4dcc0f433d419
history: > ✅ > ✅ > ✅ > ❌
- kselftest.dt.dt_test_unprobed_devices_sh_soc_jpeg-decoder_1a040000_jpgdec_1_0
last run: https://d.kernelci.org/test/maestro:6a3a90396de4dcc0f433d418
history: > ✅ > ✅ > ✅ > ❌
- kselftest.dt.dt_test_unprobed_devices_sh_soc_jpeg-encoder_1a030000
last run: https://d.kernelci.org/test/maestro:6a3a90396de4dcc0f433d417
history: > ✅ > ✅ > ✅ > ❌
- kselftest.dt.dt_test_unprobed_devices_sh_soc_jpeg-encoder_1a030000_jpgenc_0_0
last run: https://d.kernelci.org/test/maestro:6a3a90396de4dcc0f433d416
history: > ✅ > ✅ > ✅ > ❌
- kselftest.dt.dt_test_unprobed_devices_sh_soc_jpeg-encoder_1a030000_jpgenc_1_0
last run: https://d.kernelci.org/test/maestro:6a3a90396de4dcc0f433d415
history: > ✅ > ✅ > ✅ > ❌
- kselftest.dt.dt_test_unprobed_devices_sh_soc_ovl_1c000000
last run: https://d.kernelci.org/test/maestro:6a3a90396de4dcc0f433d3eb
history: > ✅ > ✅ > ✅ > ❌
- kselftest.dt.dt_test_unprobed_devices_sh_soc_rdma_1c002000
last run: https://d.kernelci.org/test/maestro:6a3a90396de4dcc0f433d3e0
history: > ✅ > ✅ > ✅ > ❌
- kselftest.dt.dt_test_unprobed_devices_sh_soc_video-codec_18000000
last run: https://d.kernelci.org/test/maestro:6a3a90396de4dcc0f433d3ac
history: > ✅ > ✅ > ✅ > ❌
- kselftest.dt.dt_test_unprobed_devices_sh_soc_video-codec_18000000_video-codec_10000
last run: https://d.kernelci.org/test/maestro:6a3a90396de4dcc0f433d3ab
history: > ✅ > ✅ > ✅ > ❌
- kselftest.dt.dt_test_unprobed_devices_sh_soc_video-codec_18000000_video-codec_2000
last run: https://d.kernelci.org/test/maestro:6a3a90396de4dcc0f433d3aa
history: > ✅ > ✅ > ✅ > ❌
- kselftest.dt.dt_test_unprobed_devices_sh_soc_video-codec_18000000_video-codec_25000
last run: https://d.kernelci.org/test/maestro:6a3a90396de4dcc0f433d3a9
history: > ✅ > ✅ > ✅ > ❌
- kselftest.dt.dt_test_unprobed_devices_sh_soc_video-codec_1a020000
last run: https://d.kernelci.org/test/maestro:6a3a90396de4dcc0f433d3a8
history: > ✅ > ✅ > ✅ > ❌
### FIXED REGRESSIONS
Hardware: qcs8300-ride
> Config: defconfig+lab-setup+kselftest
- Architecture/compiler: arm64/gcc-14
- kselftest.clone3
last run: https://d.kernelci.org/test/maestro:6a3a91466de4dcc0f433e0f6
history: > ❌ > ✅ > ✅ > ✅ > ✅
### UNSTABLE TESTS
Hardware: kaanapali-mtp
> Config: defconfig+arm64-chromebook+kselftest
- Architecture/compiler: arm64/gcc-14
- kselftest.efivars
last run: https://d.kernelci.org/test/maestro:6a3a9b446de4dcc0f4343739
history: > ❌ > ✅ > ❌ > ❌ > ❌
Hardware: beaglebone-black
> Config: multi_v7_defconfig
- Architecture/compiler: arm/gcc-14
- boot
last run: https://d.kernelci.org/test/maestro:6a3a8b7c6de4dcc0f433b02c
history: > ✅ > ⚠️ > ✅ > ⚠️ > ✅
Hardware: imx6dl-riotboard
> Config: multi_v7_defconfig
- Architecture/compiler: arm/gcc-14
- boot
last run: https://d.kernelci.org/test/maestro:6a3a8bb86de4dcc0f433b0dd
history: > ⚠️ > ⚠️ > ⚠️ > ✅ > ✅
Hardware: imx6dl-udoo
> Config: multi_v7_defconfig
- Architecture/compiler: arm/gcc-14
- boot
last run: https://d.kernelci.org/test/maestro:6a3a8ba86de4dcc0f433b09e
history: > ⚠️ > ✅ > ⚠️ > ✅ > ✅
Hardware: qcs8300-ride
> Config: defconfig+lab-setup+kselftest
- Architecture/compiler: arm64/gcc-14
- kselftest.timers
last run: https://d.kernelci.org/test/maestro:6a3a91706de4dcc0f433e215
history: > ✅ > ✅ > ✅ > ❌ > ✅
- kselftest.timers.timers_rtcpie
last run: https://d.kernelci.org/test/maestro:6a3a9fa66de4dcc0f43495b9
history: > ✅ > ✅ > ✅ > ❌ > ✅
Hardware: qemu-x86_64
> Config: x86_64_defconfig+lab-setup+x86-board+kselftest
- Architecture/compiler: x86_64/gcc-14
- boot
last run: https://d.kernelci.org/test/maestro:6a3a99626de4dcc0f4340a87
history: > ✅ > ⚠️ > ✅ > ✅ > ✅
Hardware: cd8180-orion-o6
> Config: defconfig+netdev+nfs-root-boot+kselftest
- Architecture/compiler: arm64/gcc-14
- kselftest.arm64
last run: https://d.kernelci.org/test/maestro:6a3aa7ad6de4dcc0f434b648
history: > ✅ > ✅ > ⚠️ > ✅ > ❌
- ltp
last run: https://d.kernelci.org/test/maestro:6a3aa7ad6de4dcc0f434b63f
history: > ✅ > ✅ > ⚠️ > ✅ > ❌
This branch has 1 pre-existing build issues. See details in the dashboard.
Sent every day if there were changes in the past 24 hours.
Legend: ✅ PASS ❌ FAIL ⚠️ INCONCLUSIVE
--
This is an experimental report format. Please send feedback in!
Talk to us at kernelci@lists.linux.dev
Made with love by the KernelCI team - https://kernelci.org
^ permalink raw reply
* linux-next: Tree for Jun 23
From: Mark Brown @ 2026-06-23 12:44 UTC (permalink / raw)
To: Linux Next Mailing List; +Cc: Linux Kernel Mailing List
[-- Attachment #1: Type: text/plain, Size: 1762 bytes --]
Hi all,
The merge window is open, so please to not addd any v7.2 material
to your linux-next included branches until after the merge window closes.
Changes since 20260622:
The device-id tree was added.
Non-merge commits (relative to Linus' tree): 2343
2167 files changed, 117241 insertions(+), 38315 deletions(-)
----------------------------------------------------------------------------
I have created today's linux-next tree at
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
(patches at https://www.kernel.org/pub/linux/kernel/next/ ). If you
are tracking the linux-next tree using git, you should not use "git pull"
to do so as that will try to merge the new linux-next release with the
old one. You should use "git fetch" and checkout or reset to the new
master.
You can see which trees have been included by looking in the Next/Trees
file in the source. There is also the merge.log file in the Next
directory. Between each merge, the tree was built with a defconfig
for arm64, an allmodconfig for x86_64, a multi_v7_defconfig for arm,
an arm64 build of various kselftests, a KUnit build and run on arm64,
and a native build of tools/perf. After the final fixups (if any), I do
an x86_64 modules_install followed by builds for x86_64 allnoconfig,
arm64 allyesconfig, powerpc allnoconfig (32 and 64 bit),
ppc44x_defconfig and pseries_le_defconfig and i386, s390, sparc and
sparc64 defconfig and htmldocs.
Below is a summary of the state of the merge.
I am currently merging 426 trees (counting Linus' and 131 trees of bug
fix patches pending for the current release).
Stats about the size of the tree over time can be seen at
http://neuling.org/linux-next-size.html .
Thanks to Paul Gortmaker for triage and bug fixes.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
^ permalink raw reply
* linux-next: Tree for Jun 22
From: Mark Brown @ 2026-06-23 12:43 UTC (permalink / raw)
To: Linux Next Mailing List; +Cc: Linux Kernel Mailing List
[-- Attachment #1: Type: text/plain, Size: 1795 bytes --]
Hi all,
The merge window is open, so please to not addd any v7.2 material
to your linux-next included branches until after the merge window closes.
Changes since 20260619:
The amdgpu tree acquired multiple conflicts with the drm tree.
Non-merge commits (relative to Linus' tree): 3121
2993 files changed, 147532 insertions(+), 59819 deletions(-)
----------------------------------------------------------------------------
I have created today's linux-next tree at
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
(patches at https://www.kernel.org/pub/linux/kernel/next/ ). If you
are tracking the linux-next tree using git, you should not use "git pull"
to do so as that will try to merge the new linux-next release with the
old one. You should use "git fetch" and checkout or reset to the new
master.
You can see which trees have been included by looking in the Next/Trees
file in the source. There is also the merge.log file in the Next
directory. Between each merge, the tree was built with a defconfig
for arm64, an allmodconfig for x86_64, a multi_v7_defconfig for arm,
an arm64 build of various kselftests, a KUnit build and run on arm64,
and a native build of tools/perf. After the final fixups (if any), I do
an x86_64 modules_install followed by builds for x86_64 allnoconfig,
arm64 allyesconfig, powerpc allnoconfig (32 and 64 bit),
ppc44x_defconfig and pseries_le_defconfig and i386, s390, sparc and
sparc64 defconfig and htmldocs.
Below is a summary of the state of the merge.
I am currently merging 425 trees (counting Linus' and 131 trees of bug
fix patches pending for the current release).
Stats about the size of the tree over time can be seen at
http://neuling.org/linux-next-size.html .
Thanks to Paul Gortmaker for triage and bug fixes.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
^ permalink raw reply
* Missing signoff in the block tree
From: Mark Brown @ 2026-06-23 12:43 UTC (permalink / raw)
To: Jens Axboe; +Cc: linux-kernel, linux-next
[-- Attachment #1: Type: text/plain, Size: 117 bytes --]
Commit
0ab5ee5a1badb ("blk-cgroup: fix UAF in __blkcg_rstat_flush()")
is missing a Signed-off-by from its author
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
^ permalink raw reply
* Re: for next: ukleinek/linux.git:device-id-rework [Was: Re: [PATCH] mod_devicetable.h: Split into per subsystem headers]
From: Mark Brown @ 2026-06-23 11:12 UTC (permalink / raw)
To: Uwe Kleine-König (The Capable Hub)
Cc: Linus Torvalds, Greg Kroah-Hartman, linux-kernel, Rob Herring,
Saravana Kannan, Bjorn Helgaas, Rafael J. Wysocki, Len Brown,
Andi Shyti, linux-next
In-Reply-To: <ajondrElYavnW6Am@monoceros>
[-- Attachment #1: Type: text/plain, Size: 940 bytes --]
On Tue, Jun 23, 2026 at 08:40:30AM +0200, Uwe Kleine-König (The Capable Hub) wrote:
> I applied this patch on top of Linus's tree and pushed it to
>
> https://git.kernel.org/pub/scm/linux/kernel/git/ukleinek/linux.git device-id-rework
> . It's on top of a "random" development state, but the next older tagged
> tree (i.e. 7.1) doesn't contain 39d260d6bc7a ("firewire: Simplify
> storing pointers in device id struct") which modifies mod_devicetable.h.
> Mark, can you please add the above branch to next, to give it some
> exposure to build bots? I don't know the timing yet, but I'd like to get
> this in before the next merge window, ideally around 7.2-rc1, depending
> on how complicated and intrusive the follow up reworks are.
I have pulled that in at the end of the merge so we'll see how that
goes, though I do note Linus' comment about it being something that
might be a better fit for a script he can run.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
^ permalink raw reply
* for next: ukleinek/linux.git:device-id-rework [Was: Re: [PATCH] mod_devicetable.h: Split into per subsystem headers]
From: Uwe Kleine-König (The Capable Hub) @ 2026-06-23 6:40 UTC (permalink / raw)
To: Mark Brown
Cc: Linus Torvalds, Greg Kroah-Hartman, linux-kernel, Rob Herring,
Saravana Kannan, Bjorn Helgaas, Rafael J. Wysocki, Len Brown,
Andi Shyti, linux-next
In-Reply-To: <CAHk-=wgYL0xJ=RaT+t1FR6Cw8E+VZkRKZjhw5h7m3FAqqNU8Hg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1232 bytes --]
Hello Mark,
On Mon, Jun 22, 2026 at 02:49:01PM -0700, Linus Torvalds wrote:
> On Mon, 22 Jun 2026 at 14:07, Uwe Kleine-König (The Capable Hub)
> <u.kleine-koenig@baylibre.com> wrote:
> >
> > If there is a general agreement that this patch implements a good idea,
>
> Ack. This seems a good direction to me. Not only because of the whole
> "don't recompile unnecessarily" build optimization (eventually - when
> drivers start using the split-up headers), but simply as a "we
> shouldn't have mixed up different and unrelated drivers in the same
> header".
I applied this patch on top of Linus's tree and pushed it to
https://git.kernel.org/pub/scm/linux/kernel/git/ukleinek/linux.git device-id-rework
. It's on top of a "random" development state, but the next older tagged
tree (i.e. 7.1) doesn't contain 39d260d6bc7a ("firewire: Simplify
storing pointers in device id struct") which modifies mod_devicetable.h.
Mark, can you please add the above branch to next, to give it some
exposure to build bots? I don't know the timing yet, but I'd like to get
this in before the next merge window, ideally around 7.2-rc1, depending
on how complicated and intrusive the follow up reworks are.
Thanks
Uwe
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
^ permalink raw reply
* [STATUS] next/master - 948efecf22e49aa4bf55bb73ec79a0ddcfd38571
From: KernelCI bot @ 2026-06-23 2:30 UTC (permalink / raw)
To: kernelci-results; +Cc: linux-next
Hello,
Status summary for next/master
Dashboard:
https://d.kernelci.org/c/next/master/948efecf22e49aa4bf55bb73ec79a0ddcfd38571/
giturl: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
branch: master
commit hash: 948efecf22e49aa4bf55bb73ec79a0ddcfd38571
origin: maestro
test start time: 2026-06-22 12:19:43.770000+00:00
Builds: 66 ✅ 2 ❌ 0 ⚠️
Boots: 170 ✅ 4 ❌ 5 ⚠️
Tests: 30591 ✅ 5153 ❌ 6594 ⚠️
### POSSIBLE REGRESSIONS
Hardware: qcs8300-ride
> Config: defconfig+lab-setup+kselftest
- Architecture/compiler: arm64/gcc-14
- kselftest.timers
last run: https://d.kernelci.org/test/maestro:6a3936ec9ab0e7cb7598d65a
history: > ✅ > ✅ > ✅ > ✅ > ❌
- kselftest.timers.timers_rtcpie
last run: https://d.kernelci.org/test/maestro:6a3941e39ab0e7cb75993be2
history: > ✅ > ✅ > ✅ > ✅ > ❌
Hardware: imx8mp-verdin-nonwifi-dahlia
> Config: defconfig+arm64-chromebook+kselftest
- Architecture/compiler: arm64/gcc-14
- kselftest.kvm
last run: https://d.kernelci.org/test/maestro:6a3930df9ab0e7cb75986967
history: > ✅ > ❌ > ❌
### FIXED REGRESSIONS
Hardware: qcs6490-rb3gen2
> Config: defconfig+lab-setup+kselftest
- Architecture/compiler: arm64/gcc-14
- kselftest.capabilities
last run: https://d.kernelci.org/test/maestro:6a3936b79ab0e7cb7598d3e7
history: > ❌ > ✅ > ✅ > ✅ > ✅
Hardware: imx8mp-evk
> Config: defconfig+lab-setup+kselftest
- Architecture/compiler: arm64/gcc-14
- kselftest.alsa
last run: https://d.kernelci.org/test/maestro:6a3936eb9ab0e7cb7598d653
history: > ❌ > ✅
Hardware: imx8mp-verdin-nonwifi-dahlia
> Config: defconfig+lab-setup+kselftest
- Architecture/compiler: arm64/gcc-14
- kselftest.dt.dt_test_unprobed_devices_sh_soc_0_bus_30800000_i2c_30a50000_eeprom_50
last run: https://d.kernelci.org/test/maestro:6a393a949ab0e7cb75990fe5
history: > ❌ > ✅ > ✅ > ✅
Hardware: mt8183-kukui-jacuzzi-juniper-sku16
> Config: defconfig+lab-setup+arm64-chromebook+CONFIG_MODULE_COMPRESS=n+CONFIG_MODULE_COMPRESS_NONE=y
- Architecture/compiler: arm64/gcc-14
- kselftest.dt.dt_test_unprobed_devices_sh_soc_dma-controller0_14001000
last run: https://d.kernelci.org/test/maestro:6a39325d9ab0e7cb75989f12
history: > ❌ > ✅ > ✅ > ✅ > ✅
- kselftest.dt.dt_test_unprobed_devices_sh_soc_dsi_14014000
last run: https://d.kernelci.org/test/maestro:6a39325d9ab0e7cb75989f0f
history: > ❌ > ✅ > ✅ > ✅ > ✅
- kselftest.dt.dt_test_unprobed_devices_sh_soc_i2c_11008000_anx7625_58
last run: https://d.kernelci.org/test/maestro:6a39325d9ab0e7cb75989f07
history: > ❌ > ✅ > ✅ > ✅ > ✅
- kselftest.dt.dt_test_unprobed_devices_sh_soc_i2c_11008000_anx7625_58_aux-bus_panel
last run: https://d.kernelci.org/test/maestro:6a39325d9ab0e7cb75989f06
history: > ❌ > ✅ > ✅ > ✅ > ✅
- kselftest.dt.dt_test_unprobed_devices_sh_soc_ovl_14008000
last run: https://d.kernelci.org/test/maestro:6a39325d9ab0e7cb75989eea
history: > ❌ > ✅ > ✅ > ✅ > ✅
- kselftest.dt.dt_test_unprobed_devices_sh_soc_ovl_14009000
last run: https://d.kernelci.org/test/maestro:6a39325d9ab0e7cb75989ee9
history: > ❌ > ✅ > ✅ > ✅ > ✅
- kselftest.dt.dt_test_unprobed_devices_sh_soc_ovl_1400a000
last run: https://d.kernelci.org/test/maestro:6a39325d9ab0e7cb75989ee8
history: > ❌ > ✅ > ✅ > ✅ > ✅
- kselftest.dt.dt_test_unprobed_devices_sh_soc_rdma_1400b000
last run: https://d.kernelci.org/test/maestro:6a39325d9ab0e7cb75989edd
history: > ❌ > ✅ > ✅ > ✅ > ✅
- kselftest.dt.dt_test_unprobed_devices_sh_soc_rdma_1400c000
last run: https://d.kernelci.org/test/maestro:6a39325d9ab0e7cb75989edc
history: > ❌ > ✅ > ✅ > ✅ > ✅
### UNSTABLE TESTS
Hardware: kaanapali-mtp
> Config: defconfig+arm64-chromebook+kselftest
- Architecture/compiler: arm64/gcc-14
- kselftest.efivars
last run: https://d.kernelci.org/test/maestro:6a3930709ab0e7cb75986520
history: > ❌ > ❌ > ✅ > ❌ > ❌
Hardware: qcs8300-ride
> Config: defconfig+lab-setup+kselftest
- Architecture/compiler: arm64/gcc-14
- kselftest.clone3
last run: https://d.kernelci.org/test/maestro:6a3936c29ab0e7cb7598d471
history: > ✅ > ❌ > ✅ > ✅ > ✅
Hardware: bcm2711-rpi-4-b
> Config: defconfig+lab-setup+kselftest
- Architecture/compiler: arm64/gcc-14
- boot
last run: https://d.kernelci.org/test/maestro:6a3936c39ab0e7cb7598d474
history: > ✅ > ⚠️ > ⚠️ > ✅ > ✅
Hardware: beaglebone-black
> Config: multi_v7_defconfig
- Architecture/compiler: arm/gcc-14
- boot
last run: https://d.kernelci.org/test/maestro:6a392f409ab0e7cb75985cbe
history: > ⚠️ > ✅ > ⚠️ > ✅ > ⚠️
Hardware: cd8180-orion-o6
> Config: defconfig+lab-setup+kselftest
- Architecture/compiler: arm64/gcc-14
- boot
last run: https://d.kernelci.org/test/maestro:6a3936969ab0e7cb7598d21c
history: > ✅ > ✅ > ✅ > ⚠️ > ✅
> Config: defconfig+netdev+nfs-root-boot+kselftest
- Architecture/compiler: arm64/gcc-14
- kselftest.arm64
last run: https://d.kernelci.org/test/maestro:6a39336d9ab0e7cb7598b785
history: > ✅ > ✅ > ✅ > ⚠️ > ✅
- ltp
last run: https://d.kernelci.org/test/maestro:6a39336d9ab0e7cb7598b77c
history: > ✅ > ✅ > ✅ > ⚠️ > ✅
Hardware: exynos850-e850-96
> Config: defconfig+lab-setup+kselftest
- Architecture/compiler: arm64/gcc-14
- boot
last run: https://d.kernelci.org/test/maestro:6a3936979ab0e7cb7598d21f
history: > ⚠️ > ⚠️ > ⚠️ > ⚠️ > ✅
- kselftest.arm64
last run: https://d.kernelci.org/test/maestro:6a3936989ab0e7cb7598d274
history: > ⚠️ > ⚠️ > ⚠️ > ⚠️ > ✅
- kselftest.breakpoints
last run: https://d.kernelci.org/test/maestro:6a3936989ab0e7cb7598d278
history: > ⚠️ > ⚠️ > ⚠️ > ⚠️ > ✅
- ltp
last run: https://d.kernelci.org/test/maestro:6a3936989ab0e7cb7598d271
history: > ⚠️ > ⚠️ > ⚠️ > ⚠️ > ✅
Hardware: imx6dl-riotboard
> Config: multi_v7_defconfig
- Architecture/compiler: arm/gcc-14
- boot
last run: https://d.kernelci.org/test/maestro:6a392f5a9ab0e7cb75985e5a
history: > ⚠️ > ⚠️ > ⚠️ > ⚠️ > ✅
Hardware: imx6dl-udoo
> Config: multi_v7_defconfig
- Architecture/compiler: arm/gcc-14
- boot
last run: https://d.kernelci.org/test/maestro:6a392f4a9ab0e7cb75985d13
history: > ✅ > ⚠️ > ✅ > ⚠️ > ✅
Hardware: qemu-x86_64
> Config: x86_64_defconfig+lab-setup+x86-board+kselftest
- Architecture/compiler: x86_64/gcc-14
- boot
last run: https://d.kernelci.org/test/maestro:6a3930769ab0e7cb7598654a
history: > ⚠️ > ✅ > ✅ > ⚠️ > ✅
This branch has 1 pre-existing build issues. See details in the dashboard.
Sent every day if there were changes in the past 24 hours.
Legend: ✅ PASS ❌ FAIL ⚠️ INCONCLUSIVE
--
This is an experimental report format. Please send feedback in!
Talk to us at kernelci@lists.linux.dev
Made with love by the KernelCI team - https://kernelci.org
^ permalink raw reply
* -next status half way through the v7.2 merge window
From: Mark Brown @ 2026-06-22 12:07 UTC (permalink / raw)
To: Linus Torvalds; +Cc: linux-next, linux-kernel
[-- Attachment #1: Type: text/plain, Size: 805 bytes --]
Hi Linus,
Everything seems very smooth at the minute, we're not even seeing many
conflicts moving around due to things being merged into your tree in a
different order to that they're merged in -next.
No trees are held at old versions, though we do still have the perf
build failure in your tree.
Trees with signoff problems:
edac (missing committer)
erofs (missing committer)
The erofs issue is new today, I got a mail saying it was already fixed.
edac is supposed to be fixed on the way to your tree.
Non-merge commits relative to Linus' tree: 3121
2993 files changed, 147532 insertions(+), 59819 deletions(-)
Top trees adding commits to -next:
383 char-misc
364 perf
199 staging
193 amdgpu
168 pci
131 usb
118 mm-stable
115 drivers-x86
87 phy-next
83 net
Thanks,
Mark
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
^ permalink raw reply
* Re: linux-next: build failure after merge of the origin tree
From: Mark Brown @ 2026-06-22 10:54 UTC (permalink / raw)
To: Alan Maguire
Cc: Linus Torvalds, Alexei Starovoitov, Arnaldo Carvalho de Melo,
Linux Kernel Mailing List, Linux Next Mailing List
In-Reply-To: <14b1b663-56fc-4272-83a1-9fee21a9d098@oracle.com>
[-- Attachment #1: Type: text/plain, Size: 291 bytes --]
On Mon, Jun 22, 2026 at 11:37:10AM +0100, Alan Maguire wrote:
> thanks for catching this; I sent [1] which should resolve the failure.
Thanks, I also sent
https://lore.kernel.org/r/20260617130038.34534-1-broonie@kernel.org
Arnaldo said he'd applied it but it's not in Linus' tree yet.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
^ permalink raw reply
* Re: Missing signoff in the erofs tree
From: Gao Xiang @ 2026-06-22 10:53 UTC (permalink / raw)
To: Mark Brown; +Cc: Gao Xiang, linux-kernel, linux-next
In-Reply-To: <ajkSK9jNJBSi4omB@sirena.org.uk>
On Mon, Jun 22, 2026 at 11:44:59AM +0100, Mark Brown wrote:
> Commit
>
> 8501551579195 ("erofs: handle 48-bit blocks_hi for compressed inodes")
>
> is missing a Signed-off-by from its committer
Thanks, fixed and pushed.
Thanks,
Gao Xiang
^ permalink raw reply
* linux-next: duplicate patch in the amdgpu tree
From: Mark Brown @ 2026-06-22 10:45 UTC (permalink / raw)
To: Alex Deucher; +Cc: Linux Kernel Mailing List, Linux Next Mailing List
[-- Attachment #1: Type: text/plain, Size: 169 bytes --]
Hi all,
The following commit is also in the drm tree as a different commit
(but the same patch):
7dba3e10ecdee ("drm/amdgpu: initialize irq.lock spinlock earlier")
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
^ permalink raw reply
* linux-next: manual merge of the amdgpu tree with the drm tree
From: Mark Brown @ 2026-06-22 10:45 UTC (permalink / raw)
To: Alex Deucher
Cc: Alex Deucher, Linux Kernel Mailing List, Linux Next Mailing List,
Tvrtko Ursulin
[-- Attachment #1: Type: text/plain, Size: 11764 bytes --]
Hi all,
Today's linux-next merge of the amdgpu tree got a conflict in:
drivers/gpu/drm/amd/amdgpu/amdgpu_ctx.c
between commit:
c1dc4ccb82c9e ("drm/amdgpu: Fix context pstate override handling")
from the drm tree and commit:
1b5e413713c0a ("drm/amdgpu: Fix context pstate override handling")
from the amdgpu tree.
diff --combined drivers/gpu/drm/amd/amdgpu/amdgpu_ctx.c
index ce35b415093d6,b15ed4a534f17..0000000000000
--- a/drivers/gpu/drm/amd/amdgpu/amdgpu_ctx.c
+++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_ctx.c
@@@ -283,6 -283,8 +283,8 @@@ static ktime_t amdgpu_ctx_fini_entity(s
if (!entity)
return res;
+ drm_sched_entity_destroy(&entity->entity);
+
for (i = 0; i < amdgpu_sched_jobs; ++i) {
res = ktime_add(res, amdgpu_ctx_fence_time(entity->fences[i]));
dma_fence_put(entity->fences[i]);
@@@ -294,32 -296,20 +296,20 @@@
return res;
}
- static int amdgpu_ctx_get_stable_pstate(struct amdgpu_ctx *ctx,
- u32 *stable_pstate)
+ static u32 amdgpu_get_stable_pstate(struct amdgpu_device *adev)
{
- struct amdgpu_device *adev = ctx->mgr->adev;
- enum amd_dpm_forced_level current_level;
-
- current_level = amdgpu_dpm_get_performance_level(adev);
-
- switch (current_level) {
+ switch (amdgpu_dpm_get_performance_level(adev)) {
case AMD_DPM_FORCED_LEVEL_PROFILE_STANDARD:
- *stable_pstate = AMDGPU_CTX_STABLE_PSTATE_STANDARD;
- break;
+ return AMDGPU_CTX_STABLE_PSTATE_STANDARD;
case AMD_DPM_FORCED_LEVEL_PROFILE_MIN_SCLK:
- *stable_pstate = AMDGPU_CTX_STABLE_PSTATE_MIN_SCLK;
- break;
+ return AMDGPU_CTX_STABLE_PSTATE_MIN_SCLK;
case AMD_DPM_FORCED_LEVEL_PROFILE_MIN_MCLK:
- *stable_pstate = AMDGPU_CTX_STABLE_PSTATE_MIN_MCLK;
- break;
+ return AMDGPU_CTX_STABLE_PSTATE_MIN_MCLK;
case AMD_DPM_FORCED_LEVEL_PROFILE_PEAK:
- *stable_pstate = AMDGPU_CTX_STABLE_PSTATE_PEAK;
- break;
+ return AMDGPU_CTX_STABLE_PSTATE_PEAK;
default:
- *stable_pstate = AMDGPU_CTX_STABLE_PSTATE_NONE;
- break;
+ return AMDGPU_CTX_STABLE_PSTATE_NONE;
}
- return 0;
}
static int amdgpu_ctx_init(struct amdgpu_ctx_mgr *mgr, int32_t priority,
@@@ -355,7 -345,7 +345,7 @@@ static int __amdgpu_ctx_set_stable_psta
enum amd_dpm_forced_level level;
struct amdgpu_ctx *current_ctx;
u32 current_stable_pstate;
- int r;
+ int r = 0;
lockdep_assert_held(&adev->pm.stable_pstate_ctx_lock);
@@@ -383,9 -373,9 +373,9 @@@
if (current_ctx && current_ctx != ctx)
return -EBUSY;
- r = amdgpu_ctx_get_stable_pstate(ctx, ¤t_stable_pstate);
- if (r || current_stable_pstate == stable_pstate)
- return r;
+ current_stable_pstate = amdgpu_get_stable_pstate(adev);
+ if (current_stable_pstate == stable_pstate)
+ return 0;
r = amdgpu_dpm_force_performance_level(adev, level);
if (r)
@@@ -416,7 -406,7 +406,7 @@@ static int amdgpu_ctx_set_stable_pstate
return r;
}
- static void amdgpu_ctx_fini(struct kref *ref)
+ void amdgpu_ctx_fini(struct kref *ref)
{
struct amdgpu_ctx *ctx = container_of(ref, struct amdgpu_ctx, refcount);
struct amdgpu_ctx_mgr *mgr = ctx->mgr;
@@@ -504,53 -494,26 +494,26 @@@ static int amdgpu_ctx_alloc(struct amdg
if (!ctx)
return -ENOMEM;
- mutex_lock(&mgr->lock);
- r = idr_alloc(&mgr->ctx_handles, ctx, 1, AMDGPU_VM_MAX_NUM_CTX, GFP_KERNEL);
- if (r < 0) {
- mutex_unlock(&mgr->lock);
+ r = amdgpu_ctx_init(mgr, priority, filp, ctx);
+ if (r) {
kfree(ctx);
return r;
}
- *id = (uint32_t)r;
- r = amdgpu_ctx_init(mgr, priority, filp, ctx);
- if (r) {
- idr_remove(&mgr->ctx_handles, *id);
- *id = 0;
- kfree(ctx);
- }
- mutex_unlock(&mgr->lock);
+ r = xa_alloc(&mgr->ctx_handles, id, ctx, xa_limit_32b, GFP_KERNEL);
+ if (r)
+ amdgpu_ctx_put(ctx);
+
return r;
}
- static void amdgpu_ctx_do_release(struct kref *ref)
- {
- struct amdgpu_ctx *ctx;
- u32 i, j;
-
- ctx = container_of(ref, struct amdgpu_ctx, refcount);
- for (i = 0; i < AMDGPU_HW_IP_NUM; ++i) {
- for (j = 0; j < amdgpu_ctx_num_entities[i]; ++j) {
- if (!ctx->entities[i][j])
- continue;
-
- drm_sched_entity_destroy(&ctx->entities[i][j]->entity);
- }
- }
-
- amdgpu_ctx_fini(ref);
- }
-
static int amdgpu_ctx_free(struct amdgpu_fpriv *fpriv, uint32_t id)
{
- struct amdgpu_ctx_mgr *mgr = &fpriv->ctx_mgr;
struct amdgpu_ctx *ctx;
- mutex_lock(&mgr->lock);
- ctx = idr_remove(&mgr->ctx_handles, id);
- if (ctx)
- kref_put(&ctx->refcount, amdgpu_ctx_do_release);
- mutex_unlock(&mgr->lock);
+ ctx = xa_erase(&fpriv->ctx_mgr.ctx_handles, id);
+ amdgpu_ctx_put(ctx);
+
return ctx ? 0 : -EINVAL;
}
@@@ -559,20 -522,12 +522,12 @@@ static int amdgpu_ctx_query(struct amdg
union drm_amdgpu_ctx_out *out)
{
struct amdgpu_ctx *ctx;
- struct amdgpu_ctx_mgr *mgr;
unsigned reset_counter;
- if (!fpriv)
+ ctx = amdgpu_ctx_get(fpriv, id);
+ if (!ctx)
return -EINVAL;
- mgr = &fpriv->ctx_mgr;
- mutex_lock(&mgr->lock);
- ctx = idr_find(&mgr->ctx_handles, id);
- if (!ctx) {
- mutex_unlock(&mgr->lock);
- return -EINVAL;
- }
-
/* TODO: these two are always zero */
out->state.flags = 0x0;
out->state.hangs = 0x0;
@@@ -586,7 -541,8 +541,8 @@@
out->state.reset_status = AMDGPU_CTX_UNKNOWN_RESET;
ctx->reset_counter_query = reset_counter;
- mutex_unlock(&mgr->lock);
+ amdgpu_ctx_put(ctx);
+
return 0;
}
@@@ -619,19 -575,11 +575,11 @@@ static int amdgpu_ctx_query2(struct amd
{
struct amdgpu_ras *con = amdgpu_ras_get_context(adev);
struct amdgpu_ctx *ctx;
- struct amdgpu_ctx_mgr *mgr;
- if (!fpriv)
+ ctx = amdgpu_ctx_get(fpriv, id);
+ if (!ctx)
return -EINVAL;
- mgr = &fpriv->ctx_mgr;
- mutex_lock(&mgr->lock);
- ctx = idr_find(&mgr->ctx_handles, id);
- if (!ctx) {
- mutex_unlock(&mgr->lock);
- return -EINVAL;
- }
-
out->state.flags = 0x0;
out->state.hangs = 0x0;
@@@ -671,7 -619,8 +619,8 @@@
msecs_to_jiffies(AMDGPU_RAS_COUNTE_DELAY_MS));
}
- mutex_unlock(&mgr->lock);
+ amdgpu_ctx_put(ctx);
+
return 0;
}
@@@ -680,26 -629,26 +629,26 @@@ static int amdgpu_ctx_stable_pstate(str
bool set, u32 *stable_pstate)
{
struct amdgpu_ctx *ctx;
- struct amdgpu_ctx_mgr *mgr;
- int r;
+ int r = 0;
- if (!fpriv)
+ ctx = amdgpu_ctx_get(fpriv, id);
+ if (!ctx)
return -EINVAL;
- mgr = &fpriv->ctx_mgr;
- mutex_lock(&mgr->lock);
- ctx = idr_find(&mgr->ctx_handles, id);
- if (!ctx) {
- mutex_unlock(&mgr->lock);
- return -EINVAL;
- }
+ /*
+ * The get path is odd in this uapi - it will check whether the context
+ * id exist, but otherwise does nothing with it. In other words, the
+ * uapi has historically been implemented as being able to query the
+ * global device state, as long as the caller supplies a random valid
+ * context id.
+ */
if (set)
r = amdgpu_ctx_set_stable_pstate(ctx, *stable_pstate);
else
- r = amdgpu_ctx_get_stable_pstate(ctx, stable_pstate);
+ *stable_pstate = amdgpu_get_stable_pstate(adev);
- mutex_unlock(&mgr->lock);
+ amdgpu_ctx_put(ctx);
return r;
}
@@@ -778,23 -727,14 +727,14 @@@ struct amdgpu_ctx *amdgpu_ctx_get(struc
mgr = &fpriv->ctx_mgr;
- mutex_lock(&mgr->lock);
- ctx = idr_find(&mgr->ctx_handles, id);
+ xa_lock(&mgr->ctx_handles);
+ ctx = xa_load(&mgr->ctx_handles, id);
if (ctx)
kref_get(&ctx->refcount);
- mutex_unlock(&mgr->lock);
+ xa_unlock(&mgr->ctx_handles);
return ctx;
}
- int amdgpu_ctx_put(struct amdgpu_ctx *ctx)
- {
- if (ctx == NULL)
- return -EINVAL;
-
- kref_put(&ctx->refcount, amdgpu_ctx_do_release);
- return 0;
- }
-
uint64_t amdgpu_ctx_add_fence(struct amdgpu_ctx *ctx,
struct drm_sched_entity *entity,
struct dma_fence *fence)
@@@ -928,8 -868,7 +868,7 @@@ void amdgpu_ctx_mgr_init(struct amdgpu_
unsigned int i;
mgr->adev = adev;
- mutex_init(&mgr->lock);
- idr_init_base(&mgr->ctx_handles, 1);
+ xa_init_flags(&mgr->ctx_handles, XA_FLAGS_ALLOC1);
for (i = 0; i < AMDGPU_HW_IP_NUM; ++i)
atomic64_set(&mgr->time_spend[i], 0);
@@@ -938,13 -877,13 +877,13 @@@
long amdgpu_ctx_mgr_entity_flush(struct amdgpu_ctx_mgr *mgr, long timeout)
{
struct amdgpu_ctx *ctx;
- struct idr *idp;
- uint32_t id, i, j;
+ unsigned long id;
+ int i, j;
- idp = &mgr->ctx_handles;
-
- mutex_lock(&mgr->lock);
- idr_for_each_entry(idp, ctx, id) {
+ xa_lock(&mgr->ctx_handles);
+ xa_for_each(&mgr->ctx_handles, id, ctx) {
+ kref_get(&ctx->refcount);
+ xa_unlock(&mgr->ctx_handles);
for (i = 0; i < AMDGPU_HW_IP_NUM; ++i) {
for (j = 0; j < amdgpu_ctx_num_entities[i]; ++j) {
struct drm_sched_entity *entity;
@@@ -956,45 -895,21 +895,21 @@@
timeout = drm_sched_entity_flush(entity, timeout);
}
}
+ amdgpu_ctx_put(ctx);
+ xa_lock(&mgr->ctx_handles);
}
- mutex_unlock(&mgr->lock);
+ xa_unlock(&mgr->ctx_handles);
return timeout;
}
- static void amdgpu_ctx_mgr_entity_fini(struct amdgpu_ctx_mgr *mgr)
- {
- struct amdgpu_ctx *ctx;
- struct idr *idp;
- uint32_t id, i, j;
-
- idp = &mgr->ctx_handles;
-
- idr_for_each_entry(idp, ctx, id) {
- if (kref_read(&ctx->refcount) != 1) {
- drm_err(adev_to_drm(mgr->adev), "ctx %p is still alive\n", ctx);
- continue;
- }
-
- for (i = 0; i < AMDGPU_HW_IP_NUM; ++i) {
- for (j = 0; j < amdgpu_ctx_num_entities[i]; ++j) {
- struct drm_sched_entity *entity;
-
- if (!ctx->entities[i][j])
- continue;
-
- entity = &ctx->entities[i][j]->entity;
- drm_sched_entity_fini(entity);
- }
- }
- kref_put(&ctx->refcount, amdgpu_ctx_fini);
- }
- }
-
void amdgpu_ctx_mgr_fini(struct amdgpu_ctx_mgr *mgr)
{
- amdgpu_ctx_mgr_entity_fini(mgr);
- idr_destroy(&mgr->ctx_handles);
- mutex_destroy(&mgr->lock);
+ struct amdgpu_ctx *ctx;
+ unsigned long id;
+
+ xa_for_each(&mgr->ctx_handles, id, ctx)
+ amdgpu_ctx_put(ctx);
+ xa_destroy(&mgr->ctx_handles);
}
void amdgpu_ctx_mgr_usage(struct amdgpu_ctx_mgr *mgr,
@@@ -1002,21 -917,21 +917,21 @@@
{
struct amdgpu_ctx *ctx;
unsigned int hw_ip, i;
- uint32_t id;
+ unsigned long id;
/*
* This is a little bit racy because it can be that a ctx or a fence are
* destroyed just in the moment we try to account them. But that is ok
* since exactly that case is explicitely allowed by the interface.
*/
- mutex_lock(&mgr->lock);
for (hw_ip = 0; hw_ip < AMDGPU_HW_IP_NUM; ++hw_ip) {
uint64_t ns = atomic64_read(&mgr->time_spend[hw_ip]);
usage[hw_ip] = ns_to_ktime(ns);
}
- idr_for_each_entry(&mgr->ctx_handles, ctx, id) {
+ xa_lock(&mgr->ctx_handles);
+ xa_for_each(&mgr->ctx_handles, id, ctx) {
for (hw_ip = 0; hw_ip < AMDGPU_HW_IP_NUM; ++hw_ip) {
for (i = 0; i < amdgpu_ctx_num_entities[hw_ip]; ++i) {
struct amdgpu_ctx_entity *centity;
@@@ -1030,5 -945,5 +945,5 @@@
}
}
}
- mutex_unlock(&mgr->lock);
+ xa_unlock(&mgr->ctx_handles);
}
I fixed it up (see below) and can carry the fix as necessary. This
is now fixed as far as linux-next is concerned, but any non trivial
conflicts should be mentioned to your upstream maintainer when your tree
is submitted for merging. You may also want to consider cooperating
with the maintainer of the conflicting tree to minimise any particularly
complex conflicts.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
^ permalink raw reply
* linux-next: manual merge of the amdgpu tree with the drm tree
From: Mark Brown @ 2026-06-22 10:45 UTC (permalink / raw)
To: Alex Deucher
Cc: Alex Deucher, Linux Kernel Mailing List, Linux Next Mailing List,
Thadeu Lima de Souza Cascardo, Tvrtko Ursulin
[-- Attachment #1: Type: text/plain, Size: 1845 bytes --]
Hi all,
Today's linux-next merge of the amdgpu tree got a conflict in:
drivers/gpu/drm/amd/amdgpu/amdgpu_device.c
between commit:
a2b270c0ecf6d ("drm/amdgpu: initialize irq.lock spinlock earlier")
from the drm tree and commits:
7dba3e10ecdee ("drm/amdgpu: initialize irq.lock spinlock earlier")
6eadd448d7e7d ("drm/amdgpu: Choose SOC15 RLC register read write functions at init time")
from the amdgpu tree.
I fixed it up (see below) and can carry the fix as necessary. This
is now fixed as far as linux-next is concerned, but any non trivial
conflicts should be mentioned to your upstream maintainer when your tree
is submitted for merging. You may also want to consider cooperating
with the maintainer of the conflicting tree to minimise any particularly
complex conflicts.
diff --combined drivers/gpu/drm/amd/amdgpu/amdgpu_device.c
index 211d30f03d25f,c66d3a24f54e8..0000000000000
--- a/drivers/gpu/drm/amd/amdgpu/amdgpu_device.c
+++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_device.c
@@@ -3677,6 -3677,10 +3677,10 @@@ static void amdgpu_device_sys_interface
amdgpu_pm_sysfs_fini(adev);
if (adev->ucode_sysfs_en)
amdgpu_ucode_sysfs_fini(adev);
+
+ amdgpu_discovery_sysfs_fini(adev);
+ amdgpu_preempt_mgr_sysfs_fini(adev);
+
amdgpu_device_attr_sysfs_fini(adev);
amdgpu_fru_sysfs_fini(adev);
@@@ -3773,6 -3777,7 +3777,7 @@@ int amdgpu_device_init(struct amdgpu_de
spin_lock_init(&adev->irq.lock);
+ amdgpu_early_init_rlc_reg_funcs(adev);
amdgpu_device_init_apu_flags(adev);
r = amdgpu_device_check_arguments(adev);
@@@ -4210,6 -4215,7 +4215,7 @@@ void amdgpu_device_fini_hw(struct amdgp
if (adev->mman.initialized)
drain_workqueue(adev->mman.bdev.wq);
+
adev->shutdown = true;
unregister_pm_notifier(&adev->pm_nb);
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
^ permalink raw reply
page: next (older) | prev (newer) | latest
- recent:[subjects (threaded)|topics (new)|topics (active)]
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox