* [STATUS] next/master - 8d6dbbbe3ba62de0a63e962ee004afb848c8e3ac
From: KernelCI bot @ 2026-06-16 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/8d6dbbbe3ba62de0a63e962ee004afb848c8e3ac/
giturl: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
branch: master
commit hash: 8d6dbbbe3ba62de0a63e962ee004afb848c8e3ac
origin: maestro
test start time: 2026-06-15 16:32:00.683000+00:00
Builds: 58 ✅ 1 ❌ 0 ⚠️
Boots: 168 ✅ 3 ❌ 5 ⚠️
Tests: 29239 ✅ 4933 ❌ 6587 ⚠️
### POSSIBLE REGRESSIONS
Hardware: glymur-crd
> Config: defconfig+lab-setup+kselftest
- Architecture/compiler: arm64/gcc-14
- kselftest.timers
last run: https://d.kernelci.org/test/maestro:6a30482da1ade4ad5d1250f0
history: > ✅ > ❌ > ❌ > ❌
> Config: defconfig+arm64-chromebook+kselftest
- Architecture/compiler: arm64/gcc-14
- kselftest.gpio
last run: https://d.kernelci.org/test/maestro:6a30377ca1ade4ad5d11aafa
history: > ✅ > ✅ > ❌ > ❌ > ❌
Hardware: kaanapali-mtp
> Config: defconfig+lab-setup+kselftest
- Architecture/compiler: arm64/gcc-14
- kselftest.timers
last run: https://d.kernelci.org/test/maestro:6a303bc2a1ade4ad5d11bccd
history: > ✅ > ✅ > ❌ > ❌ > ❌
> Config: defconfig+arm64-chromebook+kselftest
- Architecture/compiler: arm64/gcc-14
- kselftest.gpio
last run: https://d.kernelci.org/test/maestro:6a303783a1ade4ad5d11ab21
history: > ✅ > ✅ > ❌ > ❌ > ❌
Hardware: qcs615-ride
> Config: defconfig+arm64-chromebook+kselftest
- Architecture/compiler: arm64/gcc-14
- kselftest.gpio
last run: https://d.kernelci.org/test/maestro:6a30377ea1ade4ad5d11ab05
history: > ✅ > ✅ > ❌ > ❌
Hardware: qcs8300-ride
> Config: defconfig+lab-setup+kselftest
- Architecture/compiler: arm64/gcc-14
- kselftest.arm64
last run: https://d.kernelci.org/test/maestro:6a303b75a1ade4ad5d11ba9a
history: > ✅ > ✅ > ❌ > ❌ > ❌
- kselftest.timers
last run: https://d.kernelci.org/test/maestro:6a303bbfa1ade4ad5d11bcc2
history: > ✅ > ✅ > ✅ > ✅ > ❌
- kselftest.timers.timers_rtcpie
last run: https://d.kernelci.org/test/maestro:6a304689a1ade4ad5d124fb7
history: > ✅ > ✅ > ❌
> Config: defconfig+arm64-chromebook+kselftest
- Architecture/compiler: arm64/gcc-14
- kselftest.gpio
last run: https://d.kernelci.org/test/maestro:6a303780a1ade4ad5d11ab0e
history: > ✅ > ✅ > ❌ > ❌ > ❌
Hardware: x1e80100
> Config: defconfig+lab-setup+kselftest
- Architecture/compiler: arm64/gcc-14
- kselftest.timers
last run: https://d.kernelci.org/test/maestro:6a303bc5a1ade4ad5d11bcdc
history: > ✅ > ✅ > ❌ > ❌ > ❌
> Config: defconfig+arm64-chromebook+kselftest
- Architecture/compiler: arm64/gcc-14
- kselftest.gpio
last run: https://d.kernelci.org/test/maestro:6a303786a1ade4ad5d11ab2e
history: > ✅ > ✅ > ❌ > ❌ > ❌
Hardware: bcm2711-rpi-4-b
> Config: defconfig+lab-setup+kselftest
- Architecture/compiler: arm64/gcc-14
- kselftest.device_error_logs
last run: https://d.kernelci.org/test/maestro:6a303bdda1ade4ad5d11bd82
history: > ✅ > ❌ > ❌
- kselftest.device_error_logs.devices_error_logs_test_device_error_logs_py
last run: https://d.kernelci.org/test/maestro:6a304723a1ade4ad5d125098
history: > ✅ > ❌ > ❌
- kselftest.dt
last run: https://d.kernelci.org/test/maestro:6a303bf8a1ade4ad5d11be37
history: > ✅ > ❌ > ❌ > ❌ > ❌
- kselftest.dt.dt_test_unprobed_devices_sh
last run: https://d.kernelci.org/test/maestro:6a304a4fa1ade4ad5d12526b
history: > ✅ > ❌ > ❌ > ❌ > ❌
- kselftest.dt.dt_test_unprobed_devices_sh_gpu
last run: https://d.kernelci.org/test/maestro:6a304a4fa1ade4ad5d1252b1
history: > ✅ > ❌ > ❌ > ❌ > ❌
Hardware: bcm2837-rpi-3-b-plus
> Config: defconfig+lab-setup+kselftest
- Architecture/compiler: arm64/gcc-14
- kselftest.dt.dt_test_unprobed_devices_sh_gpu
last run: https://d.kernelci.org/test/maestro:6a304503a1ade4ad5d121f08
history: > ✅ > ❌ > ❌
Hardware: sm8750-mtp
> Config: defconfig+lab-setup+kselftest
- Architecture/compiler: arm64/gcc-14
- kselftest.timers
last run: https://d.kernelci.org/test/maestro:6a303bc1a1ade4ad5d11bcc8
history: > ✅ > ✅ > ❌ > ❌ > ❌
> Config: defconfig+arm64-chromebook+kselftest
- Architecture/compiler: arm64/gcc-14
- kselftest.gpio
last run: https://d.kernelci.org/test/maestro:6a303782a1ade4ad5d11ab1c
history: > ✅ > ✅ > ❌ > ❌ > ❌
Hardware: qcs6490-rb3gen2
> Config: defconfig+lab-setup+kselftest
- Architecture/compiler: arm64/gcc-14
- kselftest.breakpoints
last run: https://d.kernelci.org/test/maestro:6a303b7fa1ade4ad5d11bada
history: > ✅ > ❌ > ❌
> Config: defconfig+arm64-chromebook+kselftest
- Architecture/compiler: arm64/gcc-14
- kselftest.gpio
last run: https://d.kernelci.org/test/maestro:6a30377fa1ade4ad5d11ab09
history: > ✅ > ✅ > ❌ > ❌ > ❌
### FIXED REGRESSIONS
Hardware: kaanapali-mtp
> Config: defconfig+lab-setup+kselftest
- Architecture/compiler: arm64/gcc-14
- kselftest.coredump
last run: https://d.kernelci.org/test/maestro:6a303ba3a1ade4ad5d11bbdb
history: > ❌ > ❌ > ✅
Hardware: asus-CX3402CVA-brya
> Config: x86_64_defconfig+lab-setup+x86-board+kselftest
- Architecture/compiler: x86_64/gcc-14
- kernelci_sleep
last run: https://d.kernelci.org/test/maestro:6a30353ba1ade4ad5d11734c
history: > ❌ > ✅ > ✅
- kernelci_sleep.rtcwake-freeze-1
last run: https://d.kernelci.org/test/maestro:6a30367ca1ade4ad5d119709
history: > ❌ > ✅ > ✅
- kernelci_sleep.rtcwake-freeze-10
last run: https://d.kernelci.org/test/maestro:6a30367ca1ade4ad5d119700
history: > ❌ > ✅ > ✅
- kernelci_sleep.rtcwake-freeze-3
last run: https://d.kernelci.org/test/maestro:6a30367ca1ade4ad5d119703
history: > ❌ > ✅ > ✅
- kernelci_sleep.rtcwake-freeze-4
last run: https://d.kernelci.org/test/maestro:6a30367ca1ade4ad5d119702
history: > ❌ > ✅ > ✅
- kernelci_sleep.rtcwake-freeze-5
last run: https://d.kernelci.org/test/maestro:6a30367ca1ade4ad5d119701
history: > ❌ > ✅ > ✅
- kernelci_sleep.rtcwake-freeze-6
last run: https://d.kernelci.org/test/maestro:6a30367ca1ade4ad5d119704
history: > ❌ > ✅ > ✅
- kernelci_sleep.rtcwake-freeze-7
last run: https://d.kernelci.org/test/maestro:6a30367ca1ade4ad5d119706
history: > ❌ > ✅ > ✅
- kernelci_sleep.rtcwake-freeze-8
last run: https://d.kernelci.org/test/maestro:6a30367ca1ade4ad5d119705
history: > ❌ > ✅ > ✅
- kernelci_sleep.rtcwake-freeze-9
last run: https://d.kernelci.org/test/maestro:6a30367ca1ade4ad5d1196ff
history: > ❌ > ✅ > ✅
- kernelci_sleep.rtcwake-mem-1
last run: https://d.kernelci.org/test/maestro:6a30367ca1ade4ad5d119713
history: > ❌ > ✅ > ✅
- kernelci_sleep.rtcwake-mem-10
last run: https://d.kernelci.org/test/maestro:6a30367ca1ade4ad5d119707
history: > ❌ > ✅ > ✅
- kernelci_sleep.rtcwake-mem-3
last run: https://d.kernelci.org/test/maestro:6a30367ca1ade4ad5d119710
history: > ❌ > ✅ > ✅
- kernelci_sleep.rtcwake-mem-4
last run: https://d.kernelci.org/test/maestro:6a30367ca1ade4ad5d11970c
history: > ❌ > ✅ > ✅
- kernelci_sleep.rtcwake-mem-6
last run: https://d.kernelci.org/test/maestro:6a30367ca1ade4ad5d11970e
history: > ❌ > ✅ > ✅
- kernelci_sleep.rtcwake-mem-8
last run: https://d.kernelci.org/test/maestro:6a30367ca1ade4ad5d11970b
history: > ❌ > ✅ > ✅
- kernelci_sleep.rtcwake-mem-9
last run: https://d.kernelci.org/test/maestro:6a30367ca1ade4ad5d11970a
history: > ❌ > ✅ > ✅
### UNSTABLE TESTS
Hardware: bcm2711-rpi-4-b
> Config: defconfig+lab-setup+kselftest
- Architecture/compiler: arm64/gcc-14
- boot
last run: https://d.kernelci.org/test/maestro:6a303bafa1ade4ad5d11bc60
history: > ✅ > ✅ > ⚠️ > ✅ > ✅
Hardware: beaglebone-black
> Config: multi_v7_defconfig
- Architecture/compiler: arm/gcc-14
- boot
last run: https://d.kernelci.org/test/maestro:6a302e66a1ade4ad5d10f970
history: > ⚠️ > ✅ > ✅ > ⚠️ > ✅
Hardware: imx6dl-udoo
> Config: multi_v7_defconfig
- Architecture/compiler: arm/gcc-14
- boot
last run: https://d.kernelci.org/test/maestro:6a302e67a1ade4ad5d10f974
history: > ✅ > ⚠️ > ✅ > ⚠️ > ✅
Hardware: imx8mp-evk
> Config: defconfig+lab-setup+kselftest
- Architecture/compiler: arm64/gcc-14
- kselftest.alsa
last run: https://d.kernelci.org/test/maestro:6a303bb5a1ade4ad5d11bc96
history: > ✅ > ❌ > ✅
- kselftest.alsa.alsa_pcm-test
last run: https://d.kernelci.org/test/maestro:6a304003a1ade4ad5d12038a
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:6a303535a1ade4ad5d11733b
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: linux-next: manual merge of the drm tree with the drm-misc-fixes tree
From: Geert Uytterhoeven @ 2026-06-16 9:16 UTC (permalink / raw)
To: Mark Brown
Cc: Dave Airlie, DRI, Jani Nikula, Linux Kernel Mailing List,
Linux Next Mailing List, Maxime Ripard, Melissa Wen, Melissa Wen
In-Reply-To: <aiq-GWegHjzdYJ2S@sirena.co.uk>
Hi Mark,
On Thu, 11 Jun 2026 at 15:59, Mark Brown <broonie@kernel.org> wrote:
> Today's linux-next merge of the drm tree got a conflict in:
>
> drivers/gpu/drm/drm_atomic.c
> include/drm/drm_colorop.h
>
> between commit:
>
> 94ff735296d371 ("drm/colorop: make lut(1/3)d_interpolation props correctly behave as mutable")
>
> from the drm-misc-fixes tree and commits:
>
> 5164f7e7ff8ec7 ("drm: Rename struct drm_atomic_state to drm_atomic_commit")
> 0c44d8dc6df988 ("drm/atomic: prefer drm_printf_indent() over inline \t")
>
> from the drm 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.
You forgot to include the fix, but I can confirm the fix in linux-next
LGTM.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
^ permalink raw reply
* linux-next: build failure after merge of the drm tree
From: Mark Brown @ 2026-06-16 13:14 UTC (permalink / raw)
To: Dave Airlie, DRI, Christoph Hellwig, Vlastimil Babka,
Steven Price, Liviu Dudau
Cc: Linux Kernel Mailing List, Linux Next Mailing List
[-- Attachment #1: Type: text/plain, Size: 977 bytes --]
Hi all,
After merging the drm tree, today's linux-next build (x86_64 allmodconfig)
failed like this:
/tmp/next/build/drivers/gpu/drm/panthor/panthor_mmu.c:1251:6: error: unused variable 'ret' [-Werror,-Wunused-variable]
1251 | int ret;
| ^~~
Caused by commit
6bb0009862c5f (mm/slab: improve kmem_cache_alloc_bulk)
interacting with changes in the drm tree. I have applied the fixup
below and can carry as needed.
diff --git a/drivers/gpu/drm/panthor/panthor_mmu.c b/drivers/gpu/drm/panthor/panthor_mmu.c
index 3151de6aa1bae..10e32fe26f7e4 100644
--- a/drivers/gpu/drm/panthor/panthor_mmu.c
+++ b/drivers/gpu/drm/panthor/panthor_mmu.c
@@ -1248,7 +1248,6 @@ static int panthor_vm_op_ctx_prealloc_pts(struct panthor_vm_op_ctx *op_ctx)
{
u64 size = op_ctx->va.range;
u64 va = op_ctx->va.addr;
- int ret;
/* L1, L2 and L3 page tables.
* We could optimize L3 allocation by iterating over the sgt and merging
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
^ permalink raw reply related
* linux-next: manual merge of the block tree with the origin tree
From: Mark Brown @ 2026-06-16 14:00 UTC (permalink / raw)
To: Jens Axboe
Cc: Linus Torvalds, Linux Kernel Mailing List,
Linux Next Mailing List
Hi all,
Today's linux-next merge of the block tree got a conflict in:
io_uring/net.c
between commit:
9b40ba14edcdf ("Merge tag 'for-7.2/io_uring-20260615' of git://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux")
from the origin tree and commit:
c59e546eda5aa ("Merge branch 'for-7.2/io_uring' into for-next")
from the block 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 io_uring/net.c
index 00a7df803b99b,fd51dcaae8ad8..0000000000000
--- a/io_uring/net.c
+++ b/io_uring/net.c
@@@ -1885,7 -1886,7 +1885,7 @@@ out
* which in turn end up in mnt_want_write() which will grab the fs
* percpu start write sem. This can trigger a lockdep warning.
*/
-static int io_bind_file_create(struct sockaddr_storage *addr, int addr_len)
+static int io_bind_file_create(const struct sockaddr_storage *addr, int addr_len)
{
const struct sockaddr_un *sun;
^ permalink raw reply
* Re: linux-next: build failure after merge of the drm tree
From: Vlastimil Babka (SUSE) @ 2026-06-16 14:01 UTC (permalink / raw)
To: Mark Brown, Dave Airlie, DRI, Christoph Hellwig, Steven Price,
Liviu Dudau
Cc: Linux Kernel Mailing List, Linux Next Mailing List
In-Reply-To: <ajFMJzsbcZ1m_vr3@sirena.org.uk>
On 6/16/26 15:14, Mark Brown wrote:
> Hi all,
>
> After merging the drm tree, today's linux-next build (x86_64 allmodconfig)
> failed like this:
>
> /tmp/next/build/drivers/gpu/drm/panthor/panthor_mmu.c:1251:6: error: unused variable 'ret' [-Werror,-Wunused-variable]
> 1251 | int ret;
> | ^~~
>
> Caused by commit
>
> 6bb0009862c5f (mm/slab: improve kmem_cache_alloc_bulk)
>
> interacting with changes in the drm tree. I have applied the fixup
> below and can carry as needed.
Initially there was a conflict between drm and slab and your resolution
removed that line:
https://lore.kernel.org/all/ahoZ7OCzxTAbGMtO@sirena.org.uk/
I think nothing has changed except that the slab part was merged to mainline
since. Maybe that changed the ordering of the two trees and you had to redo
the conflict resolution?
> diff --git a/drivers/gpu/drm/panthor/panthor_mmu.c b/drivers/gpu/drm/panthor/panthor_mmu.c
> index 3151de6aa1bae..10e32fe26f7e4 100644
> --- a/drivers/gpu/drm/panthor/panthor_mmu.c
> +++ b/drivers/gpu/drm/panthor/panthor_mmu.c
> @@ -1248,7 +1248,6 @@ static int panthor_vm_op_ctx_prealloc_pts(struct panthor_vm_op_ctx *op_ctx)
> {
> u64 size = op_ctx->va.range;
> u64 va = op_ctx->va.addr;
> - int ret;
>
> /* L1, L2 and L3 page tables.
> * We could optimize L3 allocation by iterating over the sgt and merging
^ permalink raw reply
* Re: linux-next: manual merge of the block tree with the origin tree
From: Jens Axboe @ 2026-06-16 14:04 UTC (permalink / raw)
To: Mark Brown
Cc: Linus Torvalds, Linux Kernel Mailing List,
Linux Next Mailing List
In-Reply-To: <ajFXBeLQC96YuC0p@sirena.org.uk>
On 6/16/26 8:00 AM, Mark Brown wrote:
> Hi all,
>
> Today's linux-next merge of the block tree got a conflict in:
>
> io_uring/net.c
>
> between commit:
>
> 9b40ba14edcdf ("Merge tag 'for-7.2/io_uring-20260615' of git://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux")
>
> from the origin tree and commit:
>
> c59e546eda5aa ("Merge branch 'for-7.2/io_uring' into for-next")
>
> from the block 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.
I updated my for-next a few hours ago, I think you're using an older
one. Regardless, it's fine.
--
Jens Axboe
^ permalink raw reply
* Re: linux-next: manual merge of the block tree with the origin tree
From: Mark Brown @ 2026-06-16 14:10 UTC (permalink / raw)
To: Jens Axboe
Cc: Linus Torvalds, Linux Kernel Mailing List,
Linux Next Mailing List
In-Reply-To: <d968a9de-df62-4120-bc95-21483a15785a@kernel.dk>
[-- Attachment #1: Type: text/plain, Size: 612 bytes --]
On Tue, Jun 16, 2026 at 08:04:50AM -0600, Jens Axboe wrote:
> On 6/16/26 8:00 AM, Mark Brown wrote:
> > 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
> I updated my for-next a few hours ago, I think you're using an older
> one. Regardless, it's fine.
Great, thanks. I mostly do a big block of fetches before starting the
merge (sometimes I update more through the day) rather than fetching
immediately before each merge, and the notification mails are often
delayed a bit compared to when I actually did the merge.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
^ permalink raw reply
* Re: linux-next: build failure after merge of the drm tree
From: Mark Brown @ 2026-06-16 14:12 UTC (permalink / raw)
To: Vlastimil Babka (SUSE)
Cc: Dave Airlie, DRI, Christoph Hellwig, Steven Price, Liviu Dudau,
Linux Kernel Mailing List, Linux Next Mailing List
In-Reply-To: <7e0b3775-3e22-4c43-828d-6bde2fd165d5@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 694 bytes --]
On Tue, Jun 16, 2026 at 04:01:06PM +0200, Vlastimil Babka (SUSE) wrote:
> On 6/16/26 15:14, Mark Brown wrote:
> > interacting with changes in the drm tree. I have applied the fixup
> > below and can carry as needed.
> Initially there was a conflict between drm and slab and your resolution
> removed that line:
> https://lore.kernel.org/all/ahoZ7OCzxTAbGMtO@sirena.org.uk/
> I think nothing has changed except that the slab part was merged to mainline
> since. Maybe that changed the ordering of the two trees and you had to redo
> the conflict resolution?
That'll be it, it didn't turn up as a conflict with the new ordering. I
did scan through for a prior issue but nothing jumped out.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
^ permalink raw reply
* linux-next: Tree for Jun 16
From: Mark Brown @ 2026-06-16 14:30 UTC (permalink / raw)
To: Linux Next Mailing List; +Cc: Linux Kernel Mailing List
[-- Attachment #1: Type: text/plain, Size: 1782 bytes --]
Hi all,
Changes since 20260615:
The drm tree acquired a semantic conflict with the slab tree for which I
applied a fixup.
The block tree acquired a conflict with the origin tree.
The slab tree lost it's build failure.
Non-merge commits (relative to Linus' tree): 10529
10805 files changed, 726221 insertions(+), 208651 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
* Project Takeoffs
From: Donald Marvin @ 2026-06-16 18:30 UTC (permalink / raw)
To: linux-next
Hi,
It comes from City Estimating, LLC
We specialize in full cost estimates and all related bidding services for all construction projects in all 50 states. We provide our services to both general and subcontractors, as well as owners/developers, architects and engineers.
Feel free to contact me if you have any question or want to see our sample work.
Regards,
Donald Marvin
Marketing Executive
City Estimating, LLC
^ permalink raw reply
* [syzbot] linux-next build error (26)
From: syzbot @ 2026-06-16 20:06 UTC (permalink / raw)
To: linux-kernel, linux-next, sfr, syzkaller-bugs
Hello,
syzbot found the following issue on:
HEAD commit: 4fa3f5fabb30 Add linux-next specific files for 20260616
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=13c134ae580000
kernel config: https://syzkaller.appspot.com/x/.config?x=3bf71f65d7d65ae1
dashboard link: https://syzkaller.appspot.com/bug?extid=1f14a35d0c73d31555e4
compiler: Debian clang version 22.1.6 (++20260514074242+fc4aad7b5db3-1~exp1~20260514074407.73), Debian LLD 22.1.6
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+1f14a35d0c73d31555e4@syzkaller.appspotmail.com
error[E0560]: struct `blk_mq_tag_set` has no field named `ops`
error[E0560]: struct `blk_mq_tag_set` has no field named `nr_hw_queues`
error[E0560]: struct `blk_mq_tag_set` has no field named `timeout`
error[E0560]: struct `blk_mq_tag_set` has no field named `numa_node`
error[E0560]: struct `blk_mq_tag_set` has no field named `queue_depth`
error[E0560]: struct `blk_mq_tag_set` has no field named `cmd_size`
error[E0560]: struct `blk_mq_tag_set` has no field named `flags`
error[E0560]: struct `blk_mq_tag_set` has no field named `driver_data`
error[E0560]: struct `blk_mq_tag_set` has no field named `nr_maps`
error[E0609]: no field `su_group` on type `configfs_subsystem`
error[E0609]: no field `su_mutex` on type `configfs_subsystem`
error[E0609]: no field `driver_data` on type `acpi_device_id`
error[E0609]: no field `id` on type `acpi_device_id`
error[E0609]: no field `parent` on type `bindings::device`
error[E0609]: no field `release` on type `bindings::device`
error[E0609]: no field `logical_block_size` on type `bindings::queue_limits`
error[E0609]: no field `physical_block_size` on type `bindings::queue_limits`
error[E0609]: no field `features` on type `bindings::queue_limits`
error[E0609]: no field `fops` on type `gendisk`
error[E0609]: no field `disk_name` on type `gendisk`
---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzkaller@googlegroups.com.
syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title
If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)
If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report
If you want to undo deduplication, reply with:
#syz undup
^ permalink raw reply
* [STATUS] next/master - 4fa3f5fabb30bf00d7475d5a33459ea83d639bf9
From: KernelCI bot @ 2026-06-17 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/4fa3f5fabb30bf00d7475d5a33459ea83d639bf9/
giturl: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
branch: master
commit hash: 4fa3f5fabb30bf00d7475d5a33459ea83d639bf9
origin: maestro
test start time: 2026-06-16 15:01:55.145000+00:00
Builds: 65 ✅ 2 ❌ 0 ⚠️
Boots: 166 ✅ 3 ❌ 6 ⚠️
Tests: 28233 ✅ 5047 ❌ 5132 ⚠️
### POSSIBLE REGRESSIONS
Hardware: kaanapali-mtp
> Config: defconfig+lab-setup+kselftest
- Architecture/compiler: arm64/gcc-14
- kselftest.timers
last run: https://d.kernelci.org/test/maestro:6a3170eeec8c023893894be3
history: > ✅ > ❌ > ❌ > ❌ > ❌
> Config: defconfig+arm64-chromebook+kselftest
- Architecture/compiler: arm64/gcc-14
- kselftest.gpio
last run: https://d.kernelci.org/test/maestro:6a317ebeec8c02389389fc18
history: > ✅ > ❌ > ❌ > ❌ > ❌
Hardware: qcs6490-rb3gen2
> Config: defconfig+lab-setup+kselftest
- Architecture/compiler: arm64/gcc-14
- kselftest.capabilities
last run: https://d.kernelci.org/test/maestro:6a3170b1ec8c0238938947e7
history: > ✅ > ✅ > ✅ > ✅ > ❌
Hardware: qcs8300-ride
> Config: defconfig+lab-setup+kselftest
- Architecture/compiler: arm64/gcc-14
- kselftest.arm64
last run: https://d.kernelci.org/test/maestro:6a31709bec8c023893894665
history: > ✅ > ❌ > ❌ > ❌ > ❌
> Config: defconfig+arm64-chromebook+kselftest
- Architecture/compiler: arm64/gcc-14
- kselftest.gpio
last run: https://d.kernelci.org/test/maestro:6a317ebbec8c02389389fc04
history: > ✅ > ❌ > ❌ > ❌ > ❌
Hardware: sm8750-mtp
> Config: defconfig+lab-setup+kselftest
- Architecture/compiler: arm64/gcc-14
- kselftest.timers
last run: https://d.kernelci.org/test/maestro:6a3170edec8c023893894bdf
history: > ✅ > ❌ > ❌ > ❌ > ❌
> Config: defconfig+arm64-chromebook+kselftest
- Architecture/compiler: arm64/gcc-14
- kselftest.gpio
last run: https://d.kernelci.org/test/maestro:6a317ebdec8c02389389fc13
history: > ✅ > ❌ > ❌ > ❌ > ❌
Hardware: glymur-crd
> Config: defconfig+arm64-chromebook+kselftest
- Architecture/compiler: arm64/gcc-14
- kselftest.gpio
last run: https://d.kernelci.org/test/maestro:6a317eb7ec8c02389389fbf8
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:6a31ccbdec8c0238938dc693
history: > ✅ > ✅ > ✅ > ❌
Hardware: qcs615-ride
> Config: defconfig+arm64-chromebook+kselftest
- Architecture/compiler: arm64/gcc-14
- kselftest.gpio
last run: https://d.kernelci.org/test/maestro:6a317eb9ec8c02389389fbfe
history: > ✅ > ❌ > ❌ > ❌
Hardware: x1e80100
> Config: defconfig+lab-setup+kselftest
- Architecture/compiler: arm64/gcc-14
- kselftest.timers
last run: https://d.kernelci.org/test/maestro:6a3170f0ec8c023893894bff
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:6a3173d9ec8c023893897751
history: > ✅ > ✅ > ✅ > ❌
- kselftest.dt.dt_test_unprobed_devices_sh_soc_dsi_14014000
last run: https://d.kernelci.org/test/maestro:6a3173d9ec8c02389389774e
history: > ✅ > ✅ > ✅ > ❌
- kselftest.dt.dt_test_unprobed_devices_sh_soc_i2c_11008000_anx7625_58
last run: https://d.kernelci.org/test/maestro:6a3173d9ec8c023893897746
history: > ✅ > ✅ > ✅ > ❌
- kselftest.dt.dt_test_unprobed_devices_sh_soc_i2c_11008000_anx7625_58_aux-bus_panel
last run: https://d.kernelci.org/test/maestro:6a3173d9ec8c023893897745
history: > ✅ > ✅ > ✅ > ❌
- kselftest.dt.dt_test_unprobed_devices_sh_soc_ovl_14008000
last run: https://d.kernelci.org/test/maestro:6a3173d9ec8c023893897729
history: > ✅ > ✅ > ✅ > ❌
- kselftest.dt.dt_test_unprobed_devices_sh_soc_ovl_14009000
last run: https://d.kernelci.org/test/maestro:6a3173d9ec8c023893897728
history: > ✅ > ✅ > ✅ > ❌
- kselftest.dt.dt_test_unprobed_devices_sh_soc_ovl_1400a000
last run: https://d.kernelci.org/test/maestro:6a3173d9ec8c023893897727
history: > ✅ > ✅ > ✅ > ❌
- kselftest.dt.dt_test_unprobed_devices_sh_soc_rdma_1400b000
last run: https://d.kernelci.org/test/maestro:6a3173d9ec8c02389389771c
history: > ✅ > ✅ > ✅ > ❌
- kselftest.dt.dt_test_unprobed_devices_sh_soc_rdma_1400c000
last run: https://d.kernelci.org/test/maestro:6a3173d9ec8c02389389771b
history: > ✅ > ✅ > ✅ > ❌
### FIXED REGRESSIONS
No fixed regressions observed.
### UNSTABLE TESTS
Hardware: kaanapali-mtp
> Config: defconfig+lab-setup+kselftest
- Architecture/compiler: arm64/gcc-14
- kselftest.coredump
last run: https://d.kernelci.org/test/maestro:6a3170ccec8c0238938948e4
history: > ❌ > ✅ > ❌
Hardware: qcs8300-ride
> Config: defconfig+lab-setup+kselftest
- Architecture/compiler: arm64/gcc-14
- kselftest.timers
last run: https://d.kernelci.org/test/maestro:6a3170ebec8c023893894bac
history: > ✅ > ✅ > ✅ > ❌ > ✅
- kselftest.timers.timers_rtcpie
last run: https://d.kernelci.org/test/maestro:6a3188b2ec8c0238938a454c
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:6a31710fec8c023893894cdc
history: > ✅ > ✅ > ⚠️ > ✅ > ✅
Hardware: beaglebone-black
> Config: multi_v7_defconfig
- Architecture/compiler: arm/gcc-14
- boot
last run: https://d.kernelci.org/test/maestro:6a316d2cec8c02389388cfb0
history: > ✅ > ⚠️ > ✅ > ✅ > ⚠️
Hardware: imx6dl-riotboard
> Config: multi_v7_defconfig
- Architecture/compiler: arm/gcc-14
- boot
last run: https://d.kernelci.org/test/maestro:6a316d2dec8c02389388cfbd
history: > ✅ > ✅ > ✅ > ⚠️
Hardware: imx6dl-udoo
> Config: multi_v7_defconfig
- Architecture/compiler: arm/gcc-14
- boot
last run: https://d.kernelci.org/test/maestro:6a316d39ec8c02389388d01e
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:6a318777ec8c0238938a3c88
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: build failure after merge of the origin tree
From: Mark Brown @ 2026-06-17 15:02 UTC (permalink / raw)
To: Linus Torvalds, Alan Maguire, Alexei Starovoitov,
Arnaldo Carvalho de Melo
Cc: Linux Kernel Mailing List, Linux Next Mailing List
[-- Attachment #1: Type: text/plain, Size: 2124 bytes --]
Hi all,
After merging the origin tree, today's linux-next build (perf.log perf)
failed like this:
util/btf.c: In function '__btf_type__find_member_by_name':
util/btf.c:19:43: error: comparison of integer expressions of different signedness: 'int' and '__u32' {aka 'unsigned int'} [-Werror=sign-compare]
19 | for (i = 0, m = btf_members(t); i < btf_vlen(t); i++, m++) {
| ^
cc1: all warnings being treated as errors
Triggered by commit:
f7a6b9eaff3e6 (bpf: Extend BTF UAPI vlen, kinds to use unused bits)
This was dealt with in -next as part of a conflict resolution,
converting i to a u32, but that doesn't seem to have been picked up
anywhere. I will apply the fixup below (which I'll also send
separately).
From 47cd4a2a08f874af25930c14437633af43a4a69c Mon Sep 17 00:00:00 2001
From: Mark Brown <broonie@kernel.org>
Date: Wed, 17 Jun 2026 13:42:10 +0100
Subject: [PATCH] perf: Fix up build failure due to bpf changes
Fix
util/btf.c: In function '__btf_type__find_member_by_name':
util/btf.c:19:43: error: comparison of integer expressions of different signedness: 'int' and '__u32' {aka 'unsigned int'} [-Werror=sign-compare]
19 | for (i = 0, m = btf_members(t); i < btf_vlen(t); i++, m++) {
| ^
cc1: all warnings being treated as errors
by making the variable the same type as the function.
Signed-off-by: Mark Brown <broonie@kernel.org>
---
tools/perf/util/btf.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tools/perf/util/btf.c b/tools/perf/util/btf.c
index bb163fe87767c..50d98f3e83bf0 100644
--- a/tools/perf/util/btf.c
+++ b/tools/perf/util/btf.c
@@ -14,7 +14,7 @@ const struct btf_member *__btf_type__find_member_by_name(struct btf *btf,
{
const struct btf_type *t = btf__type_by_id(btf, type_id);
const struct btf_member *m;
- int i;
+ u32 i;
for (i = 0, m = btf_members(t); i < btf_vlen(t); i++, m++) {
const char *current_member_name = btf__name_by_offset(btf, m->name_off);
--
2.47.3
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
^ permalink raw reply related
* linux-next: Tree for Jun 17
From: Mark Brown @ 2026-06-17 15:02 UTC (permalink / raw)
To: Linux Next Mailing List; +Cc: Linux Kernel Mailing List
[-- Attachment #1: Type: text/plain, Size: 1803 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 20260615:
The origin tree acquired a build failure for which I applied a fixup.
Non-merge commits (relative to Linus' tree): 6079
5884 files changed, 298566 insertions(+), 109672 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: Tree for Jun 17
From: Heiko Carstens @ 2026-06-18 5:12 UTC (permalink / raw)
To: Mark Brown; +Cc: Linux Next Mailing List, Linux Kernel Mailing List
In-Reply-To: <ajK3HJdAhHJ85wYq@sirena.org.uk>
On Wed, Jun 17, 2026 at 04:02:52PM +0100, Mark Brown wrote:
> 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 20260615:
>
> The origin tree acquired a build failure for which I applied a fixup.
>
> Non-merge commits (relative to Linus' tree): 6079
> 5884 files changed, 298566 insertions(+), 109672 deletions(-)
>
> ----------------------------------------------------------------------------
>
> I have created today's linux-next tree at
> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
Any chance you forgot to push next-20260617 to git.kernel.org?
At least I can see only next-20260616, including the corresponding
master branch.
^ permalink raw reply
* Re: linux-next: Tree for Jun 17
From: Mark Brown @ 2026-06-18 11:18 UTC (permalink / raw)
To: Heiko Carstens; +Cc: Linux Next Mailing List, Linux Kernel Mailing List
In-Reply-To: <20260618051211.11310Bd9-hca@linux.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 257 bytes --]
On Thu, Jun 18, 2026 at 07:12:11AM +0200, Heiko Carstens wrote:
> Any chance you forgot to push next-20260617 to git.kernel.org?
> At least I can see only next-20260616, including the corresponding
> master branch.
Yes, it wasn't pushed - it's there now.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
^ permalink raw reply
* linux-next: Tree for Jun 18
From: Mark Brown @ 2026-06-18 13:59 UTC (permalink / raw)
To: Linux Next Mailing List; +Cc: Linux Kernel Mailing List
[-- Attachment #1: Type: text/plain, Size: 1746 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 20260617:
None.
Non-merge commits (relative to Linus' tree): 5214
5042 files changed, 257308 insertions(+), 111742 deletions(-)
----------------------------------------------------------------------------
I have really 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 - 598c7067dd8b65b93f3ccada47e9014a13137f1b
From: KernelCI bot @ 2026-06-19 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/598c7067dd8b65b93f3ccada47e9014a13137f1b/
giturl: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
branch: master
commit hash: 598c7067dd8b65b93f3ccada47e9014a13137f1b
origin: maestro
test start time: 2026-06-18 14:31:10.542000+00:00
Builds: 65 ✅ 2 ❌ 0 ⚠️
Boots: 199 ✅ 3 ❌ 6 ⚠️
Tests: 28762 ✅ 4823 ❌ 5577 ⚠️
### POSSIBLE REGRESSIONS
No possible regressions observed.
### FIXED REGRESSIONS
Hardware: kaanapali-mtp
> Config: defconfig+arm64-chromebook+kselftest
- Architecture/compiler: arm64/gcc-14
- kselftest.efivars
last run: https://d.kernelci.org/test/maestro:6a3409a0ec8c0238939a5d8b
history: > ❌ > ❌ > ❌ > ❌ > ✅
### UNSTABLE TESTS
Hardware: kaanapali-mtp
> Config: defconfig+lab-setup+kselftest
- Architecture/compiler: arm64/gcc-14
- kselftest.coredump
last run: https://d.kernelci.org/test/maestro:6a340fa3ec8c0238939a90a1
history: > ❌ > ✅ > ❌ > ❌ > ❌
Hardware: qcs6490-rb3gen2
> Config: defconfig+lab-setup+kselftest
- Architecture/compiler: arm64/gcc-14
- kselftest.capabilities
last run: https://d.kernelci.org/test/maestro:6a340f8aec8c0238939a8fec
history: > ✅ > ✅ > ❌ > ✅ > ✅
Hardware: qcs8300-ride
> Config: defconfig+lab-setup+kselftest
- Architecture/compiler: arm64/gcc-14
- kselftest.clone3
last run: https://d.kernelci.org/test/maestro:6a340f95ec8c0238939a903d
history: > ✅ > ✅ > ✅ > ❌ > ✅
- kselftest.timers
last run: https://d.kernelci.org/test/maestro:6a340fc0ec8c0238939a9115
history: > ✅ > ❌ > ✅ > ✅ > ✅
- kselftest.timers.timers_rtcpie
last run: https://d.kernelci.org/test/maestro:6a34186fec8c0238939b3b32
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:6a340fd2ec8c0238939a9182
history: > ⚠️ > ✅ > ⚠️ > ✅ > ✅
Hardware: beaglebone-black
> Config: multi_v7_defconfig
- Architecture/compiler: arm/gcc-14
- boot
last run: https://d.kernelci.org/test/maestro:6a341048ec8c0238939a9469
history: > ✅ > ⚠️ > ✅ > ✅ > ⚠️
Hardware: imx6dl-riotboard
> Config: multi_v7_defconfig
- Architecture/compiler: arm/gcc-14
- boot
last run: https://d.kernelci.org/test/maestro:6a341048ec8c0238939a9473
history: > ✅ > ⚠️ > ⚠️ > ⚠️
Hardware: imx6dl-udoo
> Config: multi_v7_defconfig
- Architecture/compiler: arm/gcc-14
- boot
last run: https://d.kernelci.org/test/maestro:6a341052ec8c0238939a94da
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:6a341369ec8c0238939ad721
history: > ✅ > ✅ > ❌ > ✅ > ✅
> Config: defconfig+arm64-chromebook+kselftest
- Architecture/compiler: arm64/gcc-14
- kselftest.kvm
last run: https://d.kernelci.org/test/maestro:6a3409efec8c0238939a5f19
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:6a340770ec8c0238939a311b
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:6a340c88ec8c0238939a7c83
history: > ✅ > ✅ > ❌ > ✅ > ✅
- kselftest.dt.dt_test_unprobed_devices_sh_soc_dsi_14014000
last run: https://d.kernelci.org/test/maestro:6a340c88ec8c0238939a7c80
history: > ✅ > ✅ > ❌ > ✅ > ✅
- kselftest.dt.dt_test_unprobed_devices_sh_soc_i2c_11008000_anx7625_58
last run: https://d.kernelci.org/test/maestro:6a340c88ec8c0238939a7c78
history: > ✅ > ✅ > ❌ > ✅ > ✅
- kselftest.dt.dt_test_unprobed_devices_sh_soc_i2c_11008000_anx7625_58_aux-bus_panel
last run: https://d.kernelci.org/test/maestro:6a340c88ec8c0238939a7c77
history: > ✅ > ✅ > ❌ > ✅ > ✅
- kselftest.dt.dt_test_unprobed_devices_sh_soc_ovl_14008000
last run: https://d.kernelci.org/test/maestro:6a340c88ec8c0238939a7c5b
history: > ✅ > ✅ > ❌ > ✅ > ✅
- kselftest.dt.dt_test_unprobed_devices_sh_soc_ovl_14009000
last run: https://d.kernelci.org/test/maestro:6a340c88ec8c0238939a7c5a
history: > ✅ > ✅ > ❌ > ✅ > ✅
- kselftest.dt.dt_test_unprobed_devices_sh_soc_ovl_1400a000
last run: https://d.kernelci.org/test/maestro:6a340c88ec8c0238939a7c59
history: > ✅ > ✅ > ❌ > ✅ > ✅
- kselftest.dt.dt_test_unprobed_devices_sh_soc_rdma_1400b000
last run: https://d.kernelci.org/test/maestro:6a340c88ec8c0238939a7c4e
history: > ✅ > ✅ > ❌ > ✅ > ✅
- kselftest.dt.dt_test_unprobed_devices_sh_soc_rdma_1400c000
last run: https://d.kernelci.org/test/maestro:6a340c88ec8c0238939a7c4d
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 19
From: Mark Brown @ 2026-06-19 13:38 UTC (permalink / raw)
To: Linux Next Mailing List; +Cc: Linux Kernel Mailing List
[-- Attachment #1: Type: text/plain, Size: 1738 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 20260618:
None.
Non-merge commits (relative to Linus' tree): 4115
3842 files changed, 192426 insertions(+), 82572 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 - 3ce97bd3c4f18608335e709c24d6a40e7036cab8
From: KernelCI bot @ 2026-06-20 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/3ce97bd3c4f18608335e709c24d6a40e7036cab8/
giturl: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
branch: master
commit hash: 3ce97bd3c4f18608335e709c24d6a40e7036cab8
origin: maestro
test start time: 2026-06-19 13:17:00.107000+00:00
Builds: 66 ✅ 2 ❌ 0 ⚠️
Boots: 150 ✅ 3 ❌ 7 ⚠️
Tests: 24411 ✅ 4705 ❌ 3189 ⚠️
### POSSIBLE REGRESSIONS
Hardware: kaanapali-mtp
> Config: defconfig+lab-setup+kselftest
- Architecture/compiler: arm64/gcc-14
- kselftest.coredump
last run: https://d.kernelci.org/test/maestro:6a355130ec8c023893a16cc9
history: > ✅ > ❌ > ❌ > ❌ > ❌
### FIXED REGRESSIONS
Hardware: qcs8300-ride
> Config: defconfig+lab-setup+kselftest
- Architecture/compiler: arm64/gcc-14
- kselftest.timers
last run: https://d.kernelci.org/test/maestro:6a35514eec8c023893a16d49
history: > ❌ > ✅ > ✅ > ✅ > ✅
- kselftest.timers.timers_rtcpie
last run: https://d.kernelci.org/test/maestro:6a356841ec8c023893a1d6e1
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:6a354c25ec8c023893a1483b
history: > ❌ > ❌ > ❌ > ✅ > ❌
Hardware: qcs6490-rb3gen2
> Config: defconfig+lab-setup+kselftest
- Architecture/compiler: arm64/gcc-14
- kselftest.capabilities
last run: https://d.kernelci.org/test/maestro:6a355116ec8c023893a16c24
history: > ✅ > ❌ > ✅ > ✅ > ✅
Hardware: qcs8300-ride
> Config: defconfig+lab-setup+kselftest
- Architecture/compiler: arm64/gcc-14
- kselftest.clone3
last run: https://d.kernelci.org/test/maestro:6a355123ec8c023893a16c75
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:6a3550f4ec8c023893a16903
history: > ✅ > ⚠️ > ✅ > ✅ > ⚠️
Hardware: beaglebone-black
> Config: multi_v7_defconfig
- Architecture/compiler: arm/gcc-14
- boot
last run: https://d.kernelci.org/test/maestro:6a35470eec8c023893a092fd
history: > ✅ > ✅ > ⚠️ > ✅ > ⚠️
Hardware: cd8180-orion-o6
> Config: defconfig+lab-setup+kselftest
- Architecture/compiler: arm64/gcc-14
- boot
last run: https://d.kernelci.org/test/maestro:6a3550f4ec8c023893a16907
history: > ✅ > ✅ > ✅ > ✅ > ⚠️
> Config: defconfig+netdev+nfs-root-boot+kselftest
- Architecture/compiler: arm64/gcc-14
- kselftest.arm64
last run: https://d.kernelci.org/test/maestro:6a3553dfec8c023893a178c8
history: > ✅ > ✅ > ✅ > ✅ > ⚠️
- ltp
last run: https://d.kernelci.org/test/maestro:6a3553dfec8c023893a178bf
history: > ✅ > ✅ > ✅ > ✅ > ⚠️
Hardware: imx6dl-udoo
> Config: multi_v7_defconfig
- Architecture/compiler: arm/gcc-14
- boot
last run: https://d.kernelci.org/test/maestro:6a35471cec8c023893a0933b
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:6a354a98ec8c023893a10816
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:6a354b52ec8c023893a114de
history: > ✅ > ❌ > ✅ > ✅ > ✅
- kselftest.dt.dt_test_unprobed_devices_sh_soc_dsi_14014000
last run: https://d.kernelci.org/test/maestro:6a354b52ec8c023893a114db
history: > ✅ > ❌ > ✅ > ✅ > ✅
- kselftest.dt.dt_test_unprobed_devices_sh_soc_i2c_11008000_anx7625_58
last run: https://d.kernelci.org/test/maestro:6a354b52ec8c023893a114d3
history: > ✅ > ❌ > ✅ > ✅ > ✅
- kselftest.dt.dt_test_unprobed_devices_sh_soc_i2c_11008000_anx7625_58_aux-bus_panel
last run: https://d.kernelci.org/test/maestro:6a354b52ec8c023893a114d2
history: > ✅ > ❌ > ✅ > ✅ > ✅
- kselftest.dt.dt_test_unprobed_devices_sh_soc_ovl_14008000
last run: https://d.kernelci.org/test/maestro:6a354b52ec8c023893a114b6
history: > ✅ > ❌ > ✅ > ✅ > ✅
- kselftest.dt.dt_test_unprobed_devices_sh_soc_ovl_14009000
last run: https://d.kernelci.org/test/maestro:6a354b52ec8c023893a114b5
history: > ✅ > ❌ > ✅ > ✅ > ✅
- kselftest.dt.dt_test_unprobed_devices_sh_soc_ovl_1400a000
last run: https://d.kernelci.org/test/maestro:6a354b52ec8c023893a114b4
history: > ✅ > ❌ > ✅ > ✅ > ✅
- kselftest.dt.dt_test_unprobed_devices_sh_soc_rdma_1400b000
last run: https://d.kernelci.org/test/maestro:6a354b52ec8c023893a114a9
history: > ✅ > ❌ > ✅ > ✅ > ✅
- kselftest.dt.dt_test_unprobed_devices_sh_soc_rdma_1400c000
last run: https://d.kernelci.org/test/maestro:6a354b52ec8c023893a114a8
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: linux-next: build failure after merge of the origin tree
From: Mark Brown @ 2026-06-22 9:41 UTC (permalink / raw)
To: Linus Torvalds, Alan Maguire, Alexei Starovoitov,
Arnaldo Carvalho de Melo
Cc: Linux Kernel Mailing List, Linux Next Mailing List
In-Reply-To: <ajK3E_9sm1up6soi@sirena.org.uk>
[-- Attachment #1: Type: text/plain, Size: 711 bytes --]
On Wed, Jun 17, 2026 at 04:02:43PM +0100, Mark Brown wrote:
> Hi all,
>
> After merging the origin tree, today's linux-next build (perf.log perf)
> failed like this:
>
> util/btf.c: In function '__btf_type__find_member_by_name':
> util/btf.c:19:43: error: comparison of integer expressions of different signedness: 'int' and '__u32' {aka 'unsigned int'} [-Werror=sign-compare]
> 19 | for (i = 0, m = btf_members(t); i < btf_vlen(t); i++, m++) {
> | ^
> cc1: all warnings being treated as errors
>
> Triggered by commit:
>
> f7a6b9eaff3e6 (bpf: Extend BTF UAPI vlen, kinds to use unused bits)
This issue is still present today.
[-- 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: Alan Maguire @ 2026-06-22 10:37 UTC (permalink / raw)
To: Mark Brown, Linus Torvalds, Alexei Starovoitov,
Arnaldo Carvalho de Melo
Cc: Linux Kernel Mailing List, Linux Next Mailing List
In-Reply-To: <61b096e6-39d1-4b61-80ee-31bda9978e86@sirena.org.uk>
On 22/06/2026 10:41, Mark Brown wrote:
> On Wed, Jun 17, 2026 at 04:02:43PM +0100, Mark Brown wrote:
>> Hi all,
>>
>> After merging the origin tree, today's linux-next build (perf.log perf)
>> failed like this:
>>
>> util/btf.c: In function '__btf_type__find_member_by_name':
>> util/btf.c:19:43: error: comparison of integer expressions of different signedness: 'int' and '__u32' {aka 'unsigned int'} [-Werror=sign-compare]
>> 19 | for (i = 0, m = btf_members(t); i < btf_vlen(t); i++, m++) {
>> | ^
>> cc1: all warnings being treated as errors
>>
>> Triggered by commit:
>>
>> f7a6b9eaff3e6 (bpf: Extend BTF UAPI vlen, kinds to use unused bits)
>
> This issue is still present today.
thanks for catching this; I sent [1] which should resolve the failure.
Alan
[1] https://lore.kernel.org/all/20260622103418.579115-1-alan.maguire@oracle.com/
^ permalink raw reply
* Missing signoff in the erofs tree
From: Mark Brown @ 2026-06-22 10:44 UTC (permalink / raw)
To: Gao Xiang; +Cc: linux-kernel, linux-next
[-- Attachment #1: Type: text/plain, Size: 128 bytes --]
Commit
8501551579195 ("erofs: handle 48-bit blocks_hi for compressed inodes")
is missing a Signed-off-by from its committer
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
^ 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, Dave Airlie
Cc: Linux Kernel Mailing List, Linux Next Mailing List
[-- Attachment #1: Type: text/plain, Size: 400 bytes --]
Hi all,
The following commit is also in the drm tree as a different commit
(but the same patch):
1b5e413713c0a ("drm/amdgpu: Fix context pstate override handling")
Please note that it is the merge window and you should not be adding any
commits not intended to be merged into Linus' tree during this merge
window. Both copies of this commit were added on the same day, during
the merge window.
[-- 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