* [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: [PATCH 2/3] vmsplice: make vmsplice a trivial wrapper for preadv2/pwritev2
From: Askar Safin @ 2026-06-16 0:36 UTC (permalink / raw)
To: agordeev
Cc: akpm, axboe, brauner, david, dhowells, hch, jack, linux-api,
linux-fsdevel, linux-kernel, linux-mm, linux-next, linux-s390,
miklos, netdev, patches, pfalcato, safinaskar, torvalds, viro,
willy
In-Reply-To: <20260608171917.3195488Afc-agordeev@linux.ibm.com>
Alexander Gordeev <agordeev@linux.ibm.com>:
> Hi All,
>
> This patch as commit e2c0b2368081b ("vmsplice: make vmsplice a trivial
> wrapper for preadv2/pwritev2") in linux-next on s390 causes the selftest
> tools/testing/selftests/mm/cow.c to hang:
>
> # [RUN] vmsplice() + unmap in child ... with PTE-mapped THP (128 kB)
>
> Recently there has been changes in THP area, so the problem is not
> necessary linked to this patch per se.
>
> Please, let me know if you need any additional information.
>
> Thanks!
As well as I understand, this test uses vmsplice to pin pages.
I. e. if my patch lands, then this test should be rewriten to use
some other mechanism.
--
Askar Safin
^ permalink raw reply
* -next status as at v7.1
From: Mark Brown @ 2026-06-15 17:14 UTC (permalink / raw)
To: Linus Torvalds; +Cc: linux-next, linux-kernel
[-- Attachment #1: Type: text/plain, Size: 577 bytes --]
Hi Linus,
As you'd hope everything is fairly quiet as the merge window opens.
Trees being held at old versions:
slab next-20260612 (new today, just a forgotten push)
Trees with signoff problems:
edac (missing committer)
rpmsg (missing committer)
Non-merge commits relative to Linus' tree: 11633
12177 files changed, 756925 insertions(+), 233574 deletions(-)
Top trees adding commits to -next:
1728 drm
1608 net-next
916 arm-soc
394 v4l-dvb
383 char-misc
372 sound-asoc
336 bpf-next
321 mm-stable
307 perf
199 staging
Thanks,
Mark
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
^ permalink raw reply
* linux-next: Tree for Jun 15
From: Mark Brown @ 2026-06-15 16:44 UTC (permalink / raw)
To: Linux Next Mailing List; +Cc: Linux Kernel Mailing List
Hi all,
There was an earlier version posted briefly which I replaced due to
build errors, apologies for any disruption caused.
Changes since 20260612:
The sparc tree acquired a conflict with the mm-nonmm-unstable tree.
The hwmon-staging tree lost it's build failure.
The net-next tree acquired a conflict with the net tree.
The drm-xe tree acquired a conflict with the origin tree.
The drm-xe tree lost it's build failure.
The slab tree acquired a build failure, I used the version from
next-20260623 instead.
Non-merge commits (relative to Linus' tree): 11633
12177 files changed, 756925 insertions(+), 233574 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.
^ permalink raw reply
* Re: linux-next: build failure in final build
From: Mark Brown @ 2026-06-15 16:21 UTC (permalink / raw)
To: Vlastimil Babka; +Cc: Linux Kernel Mailing List, Linux Next Mailing List
In-Reply-To: <ajAPjq6j3hjx7dBz@sirena.org.uk>
[-- Attachment #1: Type: text/plain, Size: 265 bytes --]
On Mon, Jun 15, 2026 at 03:43:26PM +0100, Mark Brown wrote:
> Hi all,
>
> In the final build (x86_64 allnoconfig) failed like this:
...
> I have ignored this for today.
Actually this affects everything, I have used the version from 20260612
instead.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
^ permalink raw reply
* [REGRESSION] next/master: (build) too many arguments to function call, expected 5, have 6 in mm/slub...
From: KernelCI bot @ 2026-06-15 15:59 UTC (permalink / raw)
To: kernelci-results; +Cc: regressions, gus, linux-next
Hello,
New build issue found on next/master:
---
too many arguments to function call, expected 5, have 6 in mm/slub.o (mm/slub.c) [logspec:kbuild,kbuild.compiler.error]
---
- dashboard: https://d.kernelci.org/i/maestro:0c4655a413ae8e279f9ba1fcb2fc80a3953d4dd4
- giturl: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
- commit HEAD: 700f8f17ac2c84f94b7cf4420f306a23a5ddfd24
Please include the KernelCI tag when submitting a fix:
Reported-by: kernelci.org bot <bot@kernelci.org>
Log excerpt:
=====================================================
/tmp/kci/linux/mm/slub.c:5553:30: error: too many arguments to function call, expected 5, have 6
5552 | return __do_kmalloc_node(size, NULL, flags, node,
| ~~~~~~~~~~~~~~~~~
5553 | PASS_TOKEN_PARAM(token), &ac);
| ^~~
/tmp/kci/linux/mm/slub.c:5340:7: note: '__do_kmalloc_node' declared here
5340 | void *__do_kmalloc_node(kmem_buckets *b, gfp_t flags, int node,
| ^ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
5341 | kmalloc_token_t token, struct slab_alloc_context *ac)
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 error generated.
=====================================================
# Builds where the incident occurred:
## aspeed_g5_defconfig on (arm):
- compiler: clang-21
- config: None
- dashboard: https://d.kernelci.org/build/maestro:6a301b0ea1ade4ad5d108dc5
## defconfig+allnoconfig on (riscv):
- compiler: clang-21
- config: None
- dashboard: https://d.kernelci.org/build/maestro:6a301b13a1ade4ad5d108dd5
## i386_defconfig+allnoconfig on (i386):
- compiler: clang-21
- config: https://files.kernelci.org/kbuild-clang-21-i386-allnoconfig-6a301b13a1ade4ad5d108dd2/.config
- dashboard: https://d.kernelci.org/build/maestro:6a301b13a1ade4ad5d108dd2
## multi_v7_defconfig+allnoconfig on (arm):
- compiler: clang-21
- config: None
- dashboard: https://d.kernelci.org/build/maestro:6a301b0ba1ade4ad5d108dc2
## x86_64_defconfig on (x86_64):
- compiler: clang-21
- config: None
- dashboard: https://d.kernelci.org/build/maestro:6a301b17a1ade4ad5d108de4
## x86_64_defconfig+allnoconfig on (x86_64):
- compiler: clang-21
- config: None
- dashboard: https://d.kernelci.org/build/maestro:6a301b1ba1ade4ad5d108df3
#kernelci issue maestro:0c4655a413ae8e279f9ba1fcb2fc80a3953d4dd4
--
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
* [REGRESSION] next/master: (build) passing argument 1 of '__do_kmalloc_node' makes pointer from integ...
From: KernelCI bot @ 2026-06-15 15:59 UTC (permalink / raw)
To: kernelci-results; +Cc: regressions, gus, linux-next
Hello,
New build issue found on next/master:
---
passing argument 1 of '__do_kmalloc_node' makes pointer from integer without a cast [-Wint-conversion] in mm/slub.o (mm/slub.c) [logspec:kbuild,kbuild.compiler.warning]
---
- dashboard: https://d.kernelci.org/i/maestro:88b7de4573d3ff7942d5e1c391739d0d3854fe51
- giturl: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
- commit HEAD: 700f8f17ac2c84f94b7cf4420f306a23a5ddfd24
Please include the KernelCI tag when submitting a fix:
Reported-by: kernelci.org bot <bot@kernelci.org>
Log excerpt:
=====================================================
mm/slub.c:5552:42: warning: passing argument 1 of '__do_kmalloc_node' makes pointer from integer without a cast [-Wint-conversion]
5552 | return __do_kmalloc_node(size, NULL, flags, node,
| ^~~~
| |
| size_t {aka unsigned int}
mm/slub.c:5340:39: note: expected 'struct kmem_cache * (*)[15]' but argument is of type 'size_t' {aka 'unsigned int'}
5340 | void *__do_kmalloc_node(kmem_buckets *b, gfp_t flags, int node,
| ~~~~~~~~~~~~~~^
In file included from ./include/uapi/linux/posix_types.h:5,
from ./include/uapi/linux/types.h:14,
from ./include/linux/types.h:5,
from ./include/linux/kasan-checks.h:5,
from ./include/asm-generic/rwonce.h:26,
from ./arch/arc/include/generated/asm/rwonce.h:1,
from ./include/linux/compiler.h:369,
from ./arch/arc/include/asm/ptrace.h:11,
from ./arch/arc/include/asm/bug.h:11,
from ./include/linux/bug.h:5,
from ./include/linux/mmdebug.h:5,
from ./include/linux/mm.h:7,
from mm/slub.c:15:
./include/linux/stddef.h:8:14: warning: passing argument 2 of '__do_kmalloc_node' makes integer from pointer without a cast [-Wint-conversion]
8 | #define NULL ((void *)0)
| ^~~~~~~~~~~
| |
| void *
mm/slub.c:5552:48: note: in expansion of macro 'NULL'
5552 | return __do_kmalloc_node(size, NULL, flags, node,
| ^~~~
mm/slub.c:5340:48: note: expected 'gfp_t' {aka 'unsigned int'} but argument is of type 'void *'
5340 | void *__do_kmalloc_node(kmem_buckets *b, gfp_t flags, int node,
| ~~~~~~^~~~~
mm/slub.c:5552:61: error: incompatible type for argument 4 of '__do_kmalloc_node'
5552 | return __do_kmalloc_node(size, NULL, flags, node,
| ^~~~
| |
| int
mm/slub.c:5341:41: note: expected 'kmalloc_token_t' but argument is of type 'int'
5341 | kmalloc_token_t token, struct slab_alloc_context *ac)
| ~~~~~~~~~~~~~~~~^~~~~
In file included from ./include/linux/mm.h:34:
./include/linux/slab.h:520:41: error: incompatible type for argument 5 of '__do_kmalloc_node'
520 | #define PASS_TOKEN_PARAM(_token) ((kmalloc_token_t){})
| ^~~~~~~~~~~~~~~~~~~~~
| |
| kmalloc_token_t
mm/slub.c:5553:33: note: in expansion of macro 'PASS_TOKEN_PARAM'
5553 | PASS_TOKEN_PARAM(token), &ac);
| ^~~~~~~~~~~~~~~~
mm/slub.c:5341:75: note: expected 'struct slab_alloc_context *' but argument is of type 'kmalloc_token_t'
5341 | kmalloc_token_t token, struct slab_alloc_context *ac)
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~^~
mm/slub.c:5552:24: error: too many arguments to function '__do_kmalloc_node'
5552 | return __do_kmalloc_node(size, NULL, flags, node,
| ^~~~~~~~~~~~~~~~~
mm/slub.c:5340:7: note: declared here
5340 | void *__do_kmalloc_node(kmem_buckets *b, gfp_t flags, int node,
| ^~~~~~~~~~~~~~~~~
CC lib/zlib_inflate/inflate_syms.o
mm/slub.c:5558:1: error: control reaches end of non-void function [-Werror=return-type]
5558 | }
| ^
cc1: some warnings being treated as errors
=====================================================
# Builds where the incident occurred:
## haps_hs_smp_defconfig on (arc):
- compiler: gcc-14
- config: https://files.kernelci.org/kbuild-gcc-14-arc-haps_hs_smp_defconfig-6a301b2ca1ade4ad5d108e15/.config
- dashboard: https://d.kernelci.org/build/maestro:6a301b2ca1ade4ad5d108e15
#kernelci issue maestro:88b7de4573d3ff7942d5e1c391739d0d3854fe51
--
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
* [REGRESSION] next/master: (build) passing argument 1 of ‘__do_kmalloc_node’ makes pointer from integ...
From: KernelCI bot @ 2026-06-15 15:59 UTC (permalink / raw)
To: kernelci-results; +Cc: regressions, gus, linux-next
Hello,
New build issue found on next/master:
---
passing argument 1 of ‘__do_kmalloc_node’ makes pointer from integer without a cast [-Wint-conversion] in mm/slub.o (mm/slub.c) [logspec:kbuild,kbuild.compiler.error]
---
- dashboard: https://d.kernelci.org/i/maestro:54c89979f71a499b7aae008163ebb25cc99f6565
- giturl: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
- commit HEAD: 700f8f17ac2c84f94b7cf4420f306a23a5ddfd24
Please include the KernelCI tag when submitting a fix:
Reported-by: kernelci.org bot <bot@kernelci.org>
Log excerpt:
=====================================================
mm/slub.c:5552:42: error: passing argument 1 of ‘__do_kmalloc_node’ makes pointer from integer without a cast [-Wint-conversion]
5552 | return __do_kmalloc_node(size, NULL, flags, node,
| ^~~~
| |
| size_t {aka long unsigned int}
mm/slub.c:5340:39: note: expected ‘struct kmem_cache * (*)[14]’ but argument is of type ‘size_t’ {aka ‘long unsigned int’}
5340 | void *__do_kmalloc_node(kmem_buckets *b, gfp_t flags, int node,
| ~~~~~~~~~~~~~~^
In file included from ./include/uapi/linux/posix_types.h:5,
from ./include/uapi/linux/types.h:14,
from ./include/linux/types.h:5,
from ./include/linux/kasan-checks.h:5,
from ./include/asm-generic/rwonce.h:26,
from ./arch/arm64/include/asm/rwonce.h:81,
from ./include/linux/compiler.h:369,
from ./include/asm-generic/bug.h:5,
from ./arch/arm64/include/asm/bug.h:26,
from ./include/linux/bug.h:5,
from ./include/linux/mmdebug.h:5,
from ./include/linux/mm.h:7,
from mm/slub.c:15:
./include/linux/stddef.h:8:14: error: passing argument 2 of ‘__do_kmalloc_node’ makes integer from pointer without a cast [-Wint-conversion]
8 | #define NULL ((void *)0)
| ^~~~~~~~~~~
| |
| void *
mm/slub.c:5552:48: note: in expansion of macro ‘NULL’
5552 | return __do_kmalloc_node(size, NULL, flags, node,
| ^~~~
mm/slub.c:5340:48: note: expected ‘gfp_t’ {aka ‘unsigned int’} but argument is of type ‘void *’
5340 | void *__do_kmalloc_node(kmem_buckets *b, gfp_t flags, int node,
| ~~~~~~^~~~~
mm/slub.c:5552:61: error: incompatible type for argument 4 of ‘__do_kmalloc_node’
5552 | return __do_kmalloc_node(size, NULL, flags, node,
| ^~~~
| |
| int
mm/slub.c:5341:41: note: expected ‘kmalloc_token_t’ but argument is of type ‘int’
5341 | kmalloc_token_t token, struct slab_alloc_context *ac)
| ~~~~~~~~~~~~~~~~^~~~~
In file included from ./include/linux/mm.h:34:
./include/linux/slab.h:520:41: error: incompatible type for argument 5 of ‘__do_kmalloc_node’
520 | #define PASS_TOKEN_PARAM(_token) ((kmalloc_token_t){})
| ^~~~~~~~~~~~~~~~~~~~~
| |
| kmalloc_token_t
mm/slub.c:5553:33: note: in expansion of macro ‘PASS_TOKEN_PARAM’
5553 | PASS_TOKEN_PARAM(token), &ac);
| ^~~~~~~~~~~~~~~~
mm/slub.c:5341:75: note: expected ‘struct slab_alloc_context *’ but argument is of type ‘kmalloc_token_t’
5341 | kmalloc_token_t token, struct slab_alloc_context *ac)
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~^~
mm/slub.c:5552:24: error: too many arguments to function ‘__do_kmalloc_node’
5552 | return __do_kmalloc_node(size, NULL, flags, node,
| ^~~~~~~~~~~~~~~~~
mm/slub.c:5340:7: note: declared here
5340 | void *__do_kmalloc_node(kmem_buckets *b, gfp_t flags, int node,
| ^~~~~~~~~~~~~~~~~
CC lib/sys_info.o
mm/slub.c:5558:1: error: control reaches end of non-void function [-Werror=return-type]
5558 | }
| ^
cc1: some warnings being treated as errors
CC arch/arm64/kvm/hyp/nvhe/../pgtable.nvhe.o
=====================================================
# Builds where the incident occurred:
## 32r2el_defconfig on (mips):
- compiler: gcc-14
- config: https://files.kernelci.org/kbuild-gcc-14-mips-build-only-6a301bb2a1ade4ad5d1095a7/.config
- dashboard: https://d.kernelci.org/build/maestro:6a301bb2a1ade4ad5d1095a7
## 32r2el_defconfig+allnoconfig on (mips):
- compiler: gcc-14
- config: https://files.kernelci.org/kbuild-gcc-14-mips-allnoconfig-6a301baea1ade4ad5d10946c/.config
- dashboard: https://d.kernelci.org/build/maestro:6a301baea1ade4ad5d10946c
## allnoconfig on (i386):
- compiler: gcc-14
- config: https://files.kernelci.org/kbuild-gcc-14-i386-allnoconfig-6a301b9ea1ade4ad5d10944b/.config
- dashboard: https://d.kernelci.org/build/maestro:6a301b9ea1ade4ad5d10944b
## defconfig on (riscv):
- compiler: gcc-14
- config: None
- dashboard: https://d.kernelci.org/build/maestro:6a301bbaa1ade4ad5d1095b7
## defconfig+allnoconfig+lab-setup+kselftest on (arm64):
- compiler: gcc-14
- config: None
- dashboard: https://d.kernelci.org/build/maestro:6a301b62a1ade4ad5d108f4a
## defconfig+arm64-chromebook+CONFIG_RANDOMIZE_BASE=y on (arm64):
- compiler: gcc-14
- config: None
- dashboard: https://d.kernelci.org/build/maestro:6a301b74a1ade4ad5d10938b
## defconfig+kcidebug+x86-board on (i386):
- compiler: gcc-14
- config: https://files.kernelci.org/kbuild-gcc-14-x86-kcidebug-6a301bcba1ade4ad5d1095ca/.config
- dashboard: https://d.kernelci.org/build/maestro:6a301bcba1ade4ad5d1095ca
## defconfig+lab-setup+arm64-chromebook+CONFIG_MODULE_COMPRESS=n+CONFIG_MODULE_COMPRESS_NONE=y on (arm64):
- compiler: gcc-14
- config: https://files.kernelci.org/kbuild-gcc-14-arm64-chromebook-6a301af9a1ade4ad5d108d3f/.config
- dashboard: https://d.kernelci.org/build/maestro:6a301af9a1ade4ad5d108d3f
## i386_defconfig on (i386):
- compiler: gcc-14
- config: https://files.kernelci.org/kbuild-gcc-14-i386-build-only-6a301ba2a1ade4ad5d10944e/.config
- dashboard: https://d.kernelci.org/build/maestro:6a301ba2a1ade4ad5d10944e
## multi_v7_defconfig+allnoconfig on (arm):
- compiler: gcc-14
- config: None
- dashboard: https://d.kernelci.org/build/maestro:6a301b35a1ade4ad5d108e29
## multi_v7_defconfig+CONFIG_CPU_BIG_ENDIAN=y on (arm):
- compiler: gcc-14
- config: None
- dashboard: https://d.kernelci.org/build/maestro:6a301b39a1ade4ad5d108e3b
## multi_v7_defconfig+CONFIG_EFI=y+CONFIG_ARM_LPAE=y on (arm):
- compiler: gcc-14
- config: None
- dashboard: https://d.kernelci.org/build/maestro:6a301b41a1ade4ad5d108e7a
## multi_v7_defconfig+CONFIG_THUMB2_KERNEL=y on (arm):
- compiler: gcc-14
- config: None
- dashboard: https://d.kernelci.org/build/maestro:6a301b45a1ade4ad5d108e7d
## multi_v7_defconfig+kselftest on (arm):
- compiler: gcc-14
- config: None
- dashboard: https://d.kernelci.org/build/maestro:6a301b4da1ade4ad5d108e8b
## x86_64_defconfig+allnoconfig+x86-board on (x86_64):
- compiler: gcc-14
- config: None
- dashboard: https://d.kernelci.org/build/maestro:6a301bd8a1ade4ad5d1095d3
## x86_64_defconfig+aws-ec2 on (x86_64):
- compiler: gcc-14
- config: None
- dashboard: https://d.kernelci.org/build/maestro:6a301bc3a1ade4ad5d1095bd
## x86_64_defconfig+kselftest+x86-board on (x86_64):
- compiler: gcc-14
- config: None
- dashboard: https://d.kernelci.org/build/maestro:6a301bd4a1ade4ad5d1095d0
#kernelci issue maestro:54c89979f71a499b7aae008163ebb25cc99f6565
--
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 in final build
From: Mark Brown @ 2026-06-15 14:43 UTC (permalink / raw)
To: Vlastimil Babka; +Cc: Linux Kernel Mailing List, Linux Next Mailing List
[-- Attachment #1: Type: text/plain, Size: 4182 bytes --]
Hi all,
In the final build (x86_64 allnoconfig) failed like this:
/tmp/next/build/mm/slub.c: In function '__kmalloc_flags_noprof':
/tmp/next/build/mm/slub.c:5552:42: error: passing argument 1 of
'__do_kmalloc_node' makes pointer from integer without a cast
[-Wint-conversion]
5552 | return __do_kmalloc_node(size, NULL, flags, node,
| ^~~~ | size_t {aka long
| unsigned int}
/tmp/next/build/mm/slub.c:5340:39: note: expected 'struct kmem_cache *
(*)[14]' but argument is of type 'size_t' {aka 'long unsigned int'}
5340 | void *__do_kmalloc_node(kmem_buckets *b, gfp_t flags, int node,
| ~~~~~~~~~~~~~~^
In file included from /tmp/next/build/include/uapi/linux/posix_types.h:5,
from /tmp/next/build/include/uapi/linux/types.h:14,
from /tmp/next/build/include/linux/types.h:5,
from /tmp/next/build/include/linux/kasan-checks.h:5,
from /tmp/next/build/include/asm-generic/rwonce.h:26,
from /tmp/next/build/arch/arm64/include/asm/rwonce.h:81,
from /tmp/next/build/include/linux/compiler.h:369,
from /tmp/next/build/include/asm-generic/bug.h:5,
from /tmp/next/build/arch/arm64/include/asm/bug.h:26,
from /tmp/next/build/include/linux/bug.h:5,
from /tmp/next/build/include/linux/mmdebug.h:5,
from /tmp/next/build/include/linux/mm.h:7,
from /tmp/next/build/mm/slub.c:15:
/tmp/next/build/include/linux/stddef.h:8:14: error: passing argument
2 of '__do_kmalloc_node' makes integer from pointer without a cast
[-Wint-conversion]
8 | #define NULL ((void *)0)
| ^~~~~~~~~~~ | void *
/tmp/next/build/mm/slub.c:5552:48: note: in expansion of macro 'NULL'
5552 | return __do_kmalloc_node(size, NULL, flags, node,
| ^~~~
/tmp/next/build/mm/slub.c:5340:48: note: expected 'gfp_t' {aka 'unsigned
int'} but argument is of type 'void *'
5340 | void *__do_kmalloc_node(kmem_buckets *b, gfp_t flags, int node,
| ~~~~~~^~~~~
/tmp/next/build/mm/slub.c:5552:61: error: incompatible type for argument
4 of '__do_kmalloc_node'
5552 | return __do_kmalloc_node(size, NULL, flags, node,
| ^~~~
| | int
/tmp/next/build/mm/slub.c:5341:41: note: expected 'kmalloc_token_t'
but argument is of type 'int'
5341 | kmalloc_token_t token, struct slab_alloc_context *ac)
| ~~~~~~~~~~~~~~~~^~~~~
In file included from /tmp/next/build/include/linux/mm.h:34:
/tmp/next/build/include/linux/slab.h:512:41: error: incompatible type
for argument 5 of '__do_kmalloc_node'
512 | #define PASS_TOKEN_PARAM(_token) (_token)
| ^~~~~~~~ | kmalloc_token_t
/tmp/next/build/mm/slub.c:5553:33: note: in expansion of macro
'PASS_TOKEN_PARAM'
5553 | PASS_TOKEN_PARAM(token), &ac);
| ^~~~~~~~~~~~~~~~
/tmp/next/build/mm/slub.c:5341:75: note: expected 'struct
slab_alloc_context *' but argument is of type 'kmalloc_token_t'
5341 | kmalloc_token_t token, struct slab_alloc_context *ac)
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~^~
/tmp/next/build/mm/slub.c:5552:24: error: too many arguments to function
'__do_kmalloc_node'
5552 | return __do_kmalloc_node(size, NULL, flags, node,
| ^~~~~~~~~~~~~~~~~
/tmp/next/build/mm/slub.c:5340:7: note: declared here
5340 | void *__do_kmalloc_node(kmem_buckets *b, gfp_t flags, int node,
| ^~~~~~~~~~~~~~~~~
/tmp/next/build/mm/slub.c:5558:1: error: control reaches end of non-void
function [-Werror=return-type]
5558 | }
| ^
I have ignored this for today.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
^ permalink raw reply
* linux-next: duplicate patch in the drm-xe tree
From: Mark Brown @ 2026-06-15 14:43 UTC (permalink / raw)
To: Thomas Hellström, DRM XE List
Cc: Linux Kernel Mailing List, Linux Next Mailing List
[-- Attachment #1: Type: text/plain, Size: 195 bytes --]
Hi all,
The following commit is also in Linus Torvalds' tree as a different commit
(but the same patch):
b1107d085e7e8 (drm/xe: fix job timeout recovery for unstarted jobs and kernel queues)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
^ permalink raw reply
* linux-next: manual merge of the drm-xe tree with the origin tree
From: Mark Brown @ 2026-06-15 14:43 UTC (permalink / raw)
To: Thomas Hellström, DRM XE List
Cc: Linux Kernel Mailing List, Linux Next Mailing List, Matthew Brost,
Rodrigo Vivi
[-- Attachment #1: Type: text/plain, Size: 2976 bytes --]
Hi all,
Today's linux-next merge of the drm-xe tree got a conflict in:
drivers/gpu/drm/xe/xe_guc_submit.c
between commit:
347ccc0453fca ("drm/xe: fix job timeout recovery for unstarted jobs and kernel queues")
from the origin tree and commit:
b1107d085e7e8 ("drm/xe: fix job timeout recovery for unstarted jobs and kernel queues")
a889e9b06bfdb ("drm/xe: wedge from the timeout handler only after releasing the queue")
from the drm-xe 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/xe/xe_guc_submit.c
index 12a410458df6f,afe5d99cdd8bc..0000000000000
--- a/drivers/gpu/drm/xe/xe_guc_submit.c
+++ b/drivers/gpu/drm/xe/xe_guc_submit.c
@@@ -1493,7 -1493,7 +1493,7 @@@ guc_exec_queue_timedout_job(struct drm_
struct xe_device *xe = guc_to_xe(guc);
int err = -ETIME;
pid_t pid = -1;
- bool wedged = false, skip_timeout_check;
+ bool wedged = false, wedge_device = false, skip_timeout_check;
xe_gt_assert(guc_to_gt(guc), !exec_queue_destroyed(q));
@@@ -1638,7 -1638,7 +1638,7 @@@ trigger_reset
}
if (q->flags & EXEC_QUEUE_FLAG_KERNEL) {
xe_gt_WARN(q->gt, true, "Kernel-submitted job timed out\n");
- xe_device_declare_wedged(gt_to_xe(q->gt));
+ wedge_device = true;
}
} else if (q->flags & EXEC_QUEUE_FLAG_VM && !exec_queue_killed(q)) {
xe_gt_WARN(q->gt, true, "VM job timed out on non-killed execqueue\n");
@@@ -1658,6 -1658,9 +1658,9 @@@
xe_guc_exec_queue_trigger_cleanup(q);
}
+ if (wedge_device)
+ xe_device_declare_wedged(gt_to_xe(q->gt));
+
/*
* We want the job added back to the pending list so it gets freed; this
* is what DRM_GPU_SCHED_STAT_NO_HANG does.
@@@ -2241,14 -2244,6 +2244,6 @@@ static bool guc_exec_queue_reset_status
return exec_queue_reset(q) || exec_queue_killed_or_banned_or_wedged(q);
}
- static bool guc_exec_queue_active(struct xe_exec_queue *q)
- {
- struct xe_exec_queue *primary = xe_exec_queue_multi_queue_primary(q);
-
- return exec_queue_enabled(primary) &&
- !exec_queue_pending_disable(primary);
- }
-
/*
* All of these functions are an abstraction layer which other parts of Xe can
* use to trap into the GuC backend. All of these functions, aside from init,
@@@ -2268,7 -2263,6 +2263,6 @@@ static const struct xe_exec_queue_ops g
.suspend_wait = guc_exec_queue_suspend_wait,
.resume = guc_exec_queue_resume,
.reset_status = guc_exec_queue_reset_status,
- .active = guc_exec_queue_active,
};
static void guc_exec_queue_stop(struct xe_guc *guc, struct xe_exec_queue *q)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
^ permalink raw reply
* linux-next: manual merge of the net-next tree with the net tree
From: Mark Brown @ 2026-06-15 14:42 UTC (permalink / raw)
To: David Miller, Jakub Kicinski, Paolo Abeni, Networking
Cc: Aditya Garg, Linux Kernel Mailing List, Linux Next Mailing List
[-- Attachment #1: Type: text/plain, Size: 1847 bytes --]
Hi all,
Today's linux-next merge of the net-next tree got a conflict in:
drivers/net/ethernet/microsoft/mana/mana_en.c
between commit:
f8fd56977eeea ("net: mana: guard TX wq object destroy with INVALID_MANA_HANDLE check")
from the net tree and commit:
d07efe5a6e641 ("net: mana: Use per-queue allocation for tx_qp to reduce allocation size")
from the net-next 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 --cc drivers/net/ethernet/microsoft/mana/mana_en.c
index d7de4c4d25bbe,26aef21c6c2c8..0000000000000
--- a/drivers/net/ethernet/microsoft/mana/mana_en.c
+++ b/drivers/net/ethernet/microsoft/mana/mana_en.c
@@@ -2332,14 -2399,15 +2399,16 @@@ static void mana_destroy_txq(struct man
napi_synchronize(napi);
napi_disable_locked(napi);
netif_napi_del_locked(napi);
- apc->tx_qp[i].txq.napi_initialized = false;
+ apc->tx_qp[i]->txq.napi_initialized = false;
}
- mana_destroy_wq_obj(apc, GDMA_SQ, apc->tx_qp[i]->tx_object);
- if (apc->tx_qp[i].tx_object != INVALID_MANA_HANDLE)
++ if (apc->tx_qp[i]->tx_object != INVALID_MANA_HANDLE)
- mana_destroy_wq_obj(apc, GDMA_SQ, apc->tx_qp[i].tx_object);
++ mana_destroy_wq_obj(apc, GDMA_SQ, apc->tx_qp[i]->tx_object);
- mana_deinit_cq(apc, &apc->tx_qp[i].tx_cq);
+ mana_deinit_cq(apc, &apc->tx_qp[i]->tx_cq);
- mana_deinit_txq(apc, &apc->tx_qp[i].txq);
+ mana_deinit_txq(apc, &apc->tx_qp[i]->txq);
+
+ kvfree(apc->tx_qp[i]);
}
kfree(apc->tx_qp);
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
^ permalink raw reply
* linux-next: Tree for Jun 12
From: Mark Brown @ 2026-06-15 13:01 UTC (permalink / raw)
To: Linux Next Mailing List; +Cc: Linux Kernel Mailing List
[-- Attachment #1: Type: text/plain, Size: 1703 bytes --]
Hi all,
Changes since 20260611:
The vfs-brauner tree acquired a build failure due to semantic conflict
with the ksmbd tree which I fixed up.
Non-merge commits (relative to Linus' tree): 12373
13276 files changed, 815598 insertions(+), 248546 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: manual merge of the sparc tree with the mm-nonmm-unstable tree
From: Mark Brown @ 2026-06-15 13:00 UTC (permalink / raw)
To: Andreas Larsson
Cc: Andrew Morton, Linux Kernel Mailing List, Linux Next Mailing List,
Rosen Penev
[-- Attachment #1: Type: text/plain, Size: 1224 bytes --]
Hi all,
Today's linux-next merge of the sparc tree got a conflict in:
arch/sparc/include/asm/asm-prototypes.h
between commit:
4fc4802c9d563 ("sparc: add _mcount() prototype")
from the mm-nonmm-unstable tree and commits:
1919c0e50000e ("sparc: add _mcount() prototype")
2416b30ec23fd ("sparc: Export mcount for Clang-built modules")
from the sparc 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 arch/sparc/include/asm/asm-prototypes.h
index 270c51017212a,a39a24c53216b..0000000000000
--- a/arch/sparc/include/asm/asm-prototypes.h
+++ b/arch/sparc/include/asm/asm-prototypes.h
@@@ -26,6 -26,7 +26,7 @@@ void *memset(void *s, int c, size_t n)
typedef int TItype __attribute__((mode(TI)));
TItype __multi3(TItype a, TItype b);
void _mcount(void);
+ void mcount(void);
s64 __ashldi3(s64, int);
s64 __lshrdi3(s64, int);
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
^ permalink raw reply
* linux-next: duplicate patch in the sparc tree
From: Mark Brown @ 2026-06-15 13:00 UTC (permalink / raw)
To: Andreas Larsson, Andrew Morton
Cc: Linux Kernel Mailing List, Linux Next Mailing List
[-- Attachment #1: Type: text/plain, Size: 157 bytes --]
Hi all,
The following commit is also in Andrew Mortons' tree as a different commit
(but the same patch):
1919c0e50000e (sparc: add _mcount() prototype)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
^ permalink raw reply
* Re: linux-next: Tree for Jun 11 (damon)
From: Randy Dunlap @ 2026-06-14 19:03 UTC (permalink / raw)
To: SeongJae Park
Cc: Mark Brown, Linux Next Mailing List, Jiayuan Chen, damon,
Andrew Morton
In-Reply-To: <20260614184235.101552-1-sj@kernel.org>
On 6/14/26 11:42 AM, SeongJae Park wrote:
> Hello Randy,
>
> On Sun, 14 Jun 2026 10:41:05 -0700 Randy Dunlap <rdunlap@infradead.org> wrote:
>
>> Hi,
>>
>> On 6/11/26 7:33 AM, Mark Brown wrote:
>>> Hi all,
>>>
>>> Changes since 20260610:
>>>
>>
>> Please add missing kernel-doc comments:
>>
>> WARNING: ../include/linux/damon.h:909 struct member 'probes' not described in 'damon_ctx'
>> WARNING: ../include/linux/damon.h:909 struct member 'rnd_state' not described in 'damon_ctx'
>
> Thank you for notifying this!
>
> The fixes should be trivial. I made those and queued [1,2] on damon/next tree.
> DAMON patches are merged into next tree via mm.git. And mm.git is currently
> closed for non-urgent issues to focus on making things for next merge window
> stabilized. I will therefore post the fixes after the next merge window is
> closed (7.2-rc1 release).
>
> Please let me know if I'm missing something or you have any different opinion.
>
> [1] https://git.kernel.org/sj/c/892a69e2774fcface1202dbdc2ff62e433f487fa
> [2] https://git.kernel.org/sj/c/b205766e8d676b9c9e3af828e736215bc54f4690
LGTM. Thanks.
--
~Randy
^ permalink raw reply
* Re: linux-next: Tree for Jun 11 (damon)
From: SeongJae Park @ 2026-06-14 18:42 UTC (permalink / raw)
To: Randy Dunlap
Cc: SeongJae Park, Mark Brown, Linux Next Mailing List, Jiayuan Chen,
damon, Andrew Morton
In-Reply-To: <4df95955-b255-4e5a-90c4-35db02f3111f@infradead.org>
Hello Randy,
On Sun, 14 Jun 2026 10:41:05 -0700 Randy Dunlap <rdunlap@infradead.org> wrote:
> Hi,
>
> On 6/11/26 7:33 AM, Mark Brown wrote:
> > Hi all,
> >
> > Changes since 20260610:
> >
>
> Please add missing kernel-doc comments:
>
> WARNING: ../include/linux/damon.h:909 struct member 'probes' not described in 'damon_ctx'
> WARNING: ../include/linux/damon.h:909 struct member 'rnd_state' not described in 'damon_ctx'
Thank you for notifying this!
The fixes should be trivial. I made those and queued [1,2] on damon/next tree.
DAMON patches are merged into next tree via mm.git. And mm.git is currently
closed for non-urgent issues to focus on making things for next merge window
stabilized. I will therefore post the fixes after the next merge window is
closed (7.2-rc1 release).
Please let me know if I'm missing something or you have any different opinion.
[1] https://git.kernel.org/sj/c/892a69e2774fcface1202dbdc2ff62e433f487fa
[2] https://git.kernel.org/sj/c/b205766e8d676b9c9e3af828e736215bc54f4690
Thanks,
SJ
[...]
^ permalink raw reply
* Re: linux-next: Tree for Jun 11 (damon)
From: Randy Dunlap @ 2026-06-14 17:41 UTC (permalink / raw)
To: Mark Brown, Linux Next Mailing List; +Cc: Jiayuan Chen, SeongJae Park, damon
In-Reply-To: <airHKHVILKSiKTVM@sirena.co.uk>
Hi,
On 6/11/26 7:33 AM, Mark Brown wrote:
> Hi all,
>
> Changes since 20260610:
>
Please add missing kernel-doc comments:
WARNING: ../include/linux/damon.h:909 struct member 'probes' not described in 'damon_ctx'
WARNING: ../include/linux/damon.h:909 struct member 'rnd_state' not described in 'damon_ctx'
thanks.
--
~Randy
^ permalink raw reply
* [STATUS] next/master - c425609d6ac4012c8bbf01ec2e10e801b1923a7b
From: KernelCI bot @ 2026-06-13 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/c425609d6ac4012c8bbf01ec2e10e801b1923a7b/
giturl: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
branch: master
commit hash: c425609d6ac4012c8bbf01ec2e10e801b1923a7b
origin: maestro
test start time: 2026-06-12 19:04:01.109000+00:00
Builds: 57 ✅ 1 ❌ 0 ⚠️
Boots: 168 ✅ 6 ❌ 5 ⚠️
Tests: 28180 ✅ 4684 ❌ 5623 ⚠️
### 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:6a2c63ccdabb8c619d54d802
history: > ✅ > ❌ > ❌
> Config: defconfig+arm64-chromebook+kselftest
- Architecture/compiler: arm64/gcc-14
- kselftest.gpio
last run: https://d.kernelci.org/test/maestro:6a2c640ddabb8c619d54dcc8
history: > ✅ > ✅ > ❌ > ❌
Hardware: kaanapali-mtp
> Config: defconfig+lab-setup+kselftest
- Architecture/compiler: arm64/gcc-14
- kselftest.timers
last run: https://d.kernelci.org/test/maestro:6a2c63d3dabb8c619d54d846
history: > ✅ > ✅ > ❌ > ❌
> Config: defconfig+arm64-chromebook+kselftest
- Architecture/compiler: arm64/gcc-14
- kselftest.gpio
last run: https://d.kernelci.org/test/maestro:6a2c6414dabb8c619d54dcec
history: > ✅ > ✅ > ❌ > ❌
Hardware: qcs8300-ride
> Config: defconfig+lab-setup+kselftest
- Architecture/compiler: arm64/gcc-14
- kselftest.arm64
last run: https://d.kernelci.org/test/maestro:6a2c637fdabb8c619d54d414
history: > ✅ > ✅ > ❌ > ❌
> Config: defconfig+arm64-chromebook+kselftest
- Architecture/compiler: arm64/gcc-14
- kselftest.gpio
last run: https://d.kernelci.org/test/maestro:6a2c6411dabb8c619d54dcde
history: > ✅ > ✅ > ❌ > ❌
Hardware: sm8750-mtp
> Config: defconfig+lab-setup+kselftest
- Architecture/compiler: arm64/gcc-14
- kselftest.timers
last run: https://d.kernelci.org/test/maestro:6a2c63d2dabb8c619d54d841
history: > ✅ > ✅ > ❌ > ❌
> Config: defconfig+arm64-chromebook+kselftest
- Architecture/compiler: arm64/gcc-14
- kselftest.gpio
last run: https://d.kernelci.org/test/maestro:6a2c6413dabb8c619d54dce8
history: > ✅ > ✅ > ❌ > ❌
Hardware: x1e80100
> Config: defconfig+lab-setup+kselftest
- Architecture/compiler: arm64/gcc-14
- kselftest.timers
last run: https://d.kernelci.org/test/maestro:6a2c63d6dabb8c619d54d853
history: > ✅ > ✅ > ✅ > ❌ > ❌
> Config: defconfig+arm64-chromebook+kselftest
- Architecture/compiler: arm64/gcc-14
- kselftest.gpio
last run: https://d.kernelci.org/test/maestro:6a2c6417dabb8c619d54dd00
history: > ✅ > ✅ > ✅ > ❌ > ❌
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:6a2c6408dabb8c619d54dcaa
history: > ✅ > ✅ > ❌
- kselftest.dt.dt_test_unprobed_devices_sh
last run: https://d.kernelci.org/test/maestro:6a2c68bedabb8c619d55466f
history: > ✅ > ✅ > ❌
- kselftest.dt.dt_test_unprobed_devices_sh_gpu
last run: https://d.kernelci.org/test/maestro:6a2c68bedabb8c619d5546a3
history: > ✅ > ✅ > ❌
Hardware: qcs6490-rb3gen2
> Config: defconfig+lab-setup+kselftest
- Architecture/compiler: arm64/gcc-14
- kselftest.breakpoints
last run: https://d.kernelci.org/test/maestro:6a2c638adabb8c619d54d4d5
history: > ✅ > ❌
> Config: defconfig+arm64-chromebook+kselftest
- Architecture/compiler: arm64/gcc-14
- kselftest.gpio
last run: https://d.kernelci.org/test/maestro:6a2c6410dabb8c619d54dcd5
history: > ✅ > ✅ > ❌ > ❌
### FIXED REGRESSIONS
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:6a2c85a7dabb8c619d571043
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:6a2c6086dabb8c619d5461c7
history: > ❌ > ❌ > ❌ > ✅
- kernelci_sleep.rtcwake-freeze-1
last run: https://d.kernelci.org/test/maestro:6a2c61cedabb8c619d549604
history: > ❌ > ❌ > ✅
- kernelci_sleep.rtcwake-freeze-10
last run: https://d.kernelci.org/test/maestro:6a2c61cedabb8c619d5495f8
history: > ❌ > ❌ > ✅
- kernelci_sleep.rtcwake-freeze-2
last run: https://d.kernelci.org/test/maestro:6a2c61cedabb8c619d549606
history: > ❌ > ✅
- kernelci_sleep.rtcwake-freeze-3
last run: https://d.kernelci.org/test/maestro:6a2c61cedabb8c619d549608
history: > ❌ > ❌ > ✅
- kernelci_sleep.rtcwake-freeze-4
last run: https://d.kernelci.org/test/maestro:6a2c61cedabb8c619d549602
history: > ❌ > ❌ > ✅
- kernelci_sleep.rtcwake-freeze-5
last run: https://d.kernelci.org/test/maestro:6a2c61cedabb8c619d54960c
history: > ❌ > ❌ > ✅
- kernelci_sleep.rtcwake-freeze-6
last run: https://d.kernelci.org/test/maestro:6a2c61cedabb8c619d549600
history: > ❌ > ❌ > ✅
- kernelci_sleep.rtcwake-freeze-7
last run: https://d.kernelci.org/test/maestro:6a2c61cedabb8c619d5495fe
history: > ❌ > ❌ > ✅
- kernelci_sleep.rtcwake-freeze-8
last run: https://d.kernelci.org/test/maestro:6a2c61cedabb8c619d5495fa
history: > ❌ > ❌ > ✅
- kernelci_sleep.rtcwake-freeze-9
last run: https://d.kernelci.org/test/maestro:6a2c61cedabb8c619d5495fc
history: > ❌ > ❌ > ✅
- kernelci_sleep.rtcwake-mem-1
last run: https://d.kernelci.org/test/maestro:6a2c61cedabb8c619d54961e
history: > ❌ > ❌ > ✅
- kernelci_sleep.rtcwake-mem-10
last run: https://d.kernelci.org/test/maestro:6a2c61cedabb8c619d54960a
history: > ❌ > ❌ > ✅
- kernelci_sleep.rtcwake-mem-2
last run: https://d.kernelci.org/test/maestro:6a2c61cedabb8c619d54961c
history: > ❌ > ✅
- kernelci_sleep.rtcwake-mem-3
last run: https://d.kernelci.org/test/maestro:6a2c61cedabb8c619d54961a
history: > ❌ > ❌ > ✅
- kernelci_sleep.rtcwake-mem-4
last run: https://d.kernelci.org/test/maestro:6a2c61cedabb8c619d549616
history: > ❌ > ❌ > ✅
- kernelci_sleep.rtcwake-mem-5
last run: https://d.kernelci.org/test/maestro:6a2c61cedabb8c619d549618
history: > ❌ > ✅
- kernelci_sleep.rtcwake-mem-6
last run: https://d.kernelci.org/test/maestro:6a2c61cedabb8c619d549612
history: > ❌ > ❌ > ✅
- kernelci_sleep.rtcwake-mem-7
last run: https://d.kernelci.org/test/maestro:6a2c61cedabb8c619d54960e
history: > ❌ > ✅
- kernelci_sleep.rtcwake-mem-8
last run: https://d.kernelci.org/test/maestro:6a2c61cedabb8c619d549614
history: > ❌ > ❌ > ✅
- kernelci_sleep.rtcwake-mem-9
last run: https://d.kernelci.org/test/maestro:6a2c61cedabb8c619d549610
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:6a2c63bfdabb8c619d54d791
history: > ✅ > ✅ > ⚠️ > ✅ > ✅
Hardware: beaglebone-black
> Config: multi_v7_defconfig
- Architecture/compiler: arm/gcc-14
- boot
last run: https://d.kernelci.org/test/maestro:6a2c6b75dabb8c619d558c18
history: > ⚠️ > ✅ > ✅ > ⚠️ > ✅
Hardware: imx6dl-udoo
> Config: multi_v7_defconfig
- Architecture/compiler: arm/gcc-14
- boot
last run: https://d.kernelci.org/test/maestro:6a2c6b76dabb8c619d558c1b
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:6a2c6082dabb8c619d546196
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: [PATCH net-next v3 2/2] rds: convert to getsockopt_iter: manual merge
From: Jakub Kicinski @ 2026-06-13 0:44 UTC (permalink / raw)
To: Matthieu Baerts
Cc: Breno Leitao, Allison Henderson, linux-kernel, netdev, linux-rdma,
rds-devel, linux-kselftest, kernel-team, David S. Miller,
Eric Dumazet, Paolo Abeni, Simon Horman, Shuah Khan, Andy Grover,
Mark Brown, Linux Next Mailing List
In-Reply-To: <b91ff67e-ce74-4edf-a8b0-08be04586485@kernel.org>
On Fri, 12 Jun 2026 13:41:00 +0200 Matthieu Baerts wrote:
> > I was aware of the conflict but didn't realize a note would be helpful
> > for the merge. I should have included one.
> >
> > Could you point me to an example commit/patch that contains such a note so I
> > can understand the expected format and procedure?
>
> In this particular example, I think it would have been easier to have
> waited for the fix to land in net-next -- after the weekly sync with net
> -- and then send the net-next patches.
>
> When this cannot be avoided, then you can mention the conflict, and
> ideally share a diff of the resolution, plus a description, especially
> when it is not obvious, when simply saying "take the version from X" is
> helpful, when extra modifications are needed, etc. e.g. [1]. Something
> similar to what Mark is usually doing on the linux-next ML, or what I
> did here.
Thanks for explaining! This conflict was avoidable but I didn't find
the appropriately polite explanation within me :)
When conflicting code is _already committed_ to net-next we can deal
with the conflict. If there's a patch only posted but not commited and
we notice a bug - the net-next patch should be explicitly withdrawn and
reposted once the fix has propagated.
^ permalink raw reply
* Fixes tags need work in the iommu tree
From: Mark Brown @ 2026-06-12 17:17 UTC (permalink / raw)
To: Joerg Roedel; +Cc: linux-kernel, linux-next
[-- Attachment #1: Type: text/plain, Size: 418 bytes --]
In commit
db50fb87015b95 ("iommu/dma-iommu: Fix wrong scatterlist length assignment in P2PDMA path")
Fixes tag
Fixes: a25e7962db ("PCI/P2PDMA: Refactor the p2pdma mapping helpers")
has these problem(s):
- SHA1 should be at least 12 digits long
This can be fixed for the future by setting core.abbrev to 12 (or
more) or (for git v2.11 or later) just making sure it is not set
(or set to "auto").
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
^ permalink raw reply
* Missing signoff in the iommufd tree
From: Mark Brown @ 2026-06-12 17:17 UTC (permalink / raw)
To: Jason Gunthorpe; +Cc: linux-kernel, linux-next
[-- Attachment #1: Type: text/plain, Size: 341 bytes --]
Commits
7c224d21ed43fb ("iommu: Avoid copying the user array twice in the full-array copy helper")
6bbe55d4d6bc34 ("iommufd/selftest: Add invalidation entry_num and entry_len boundary tests")
105209a23e1120 ("iommufd: Set upper bounds on cache invalidation entry_num and entry_len")
are missing a Signed-off-by from their committers
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
^ permalink raw reply
* linux-next: build failure after merge of the vfs-brauner tree
From: Mark Brown @ 2026-06-12 17:17 UTC (permalink / raw)
To: Christian Brauner, Davide Ornaghi, Namjae Jeon, Steve French
Cc: Linux Kernel Mailing List, Linux Next Mailing List
[-- Attachment #1: Type: text/plain, Size: 2071 bytes --]
Hi all,
After merging the vfs-brauner tree, today's linux-next build (x86_64
allmodconfig) failed like this:
/tmp/next/build/fs/smb/server/vfs.c:1255:30: error: too many arguments to function call, expected 5, have 6
1254 | err = vfs_path_parent_lookup(filename, flags | LOOKUP_BENEATH,
| ~~~~~~~~~~~~~~~~~~~~~~
1255 | path, &last, &type, &share_conf->vfs_path);
| ^~~~~~~~~~~~~~~~~~~~~
/tmp/next/build/include/linux/namei.h:63:5: note: 'vfs_path_parent_lookup' declared here
63 | int vfs_path_parent_lookup(struct filename *filename, unsigned int flags,
| ^ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
64 | struct path *parent, struct qstr *last,
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
65 | const struct path *root);
| ~~~~~~~~~~~~~~~~~~~~~~~
1 error generated.
Caused by commit
f2f1dddccae50f (vfs: make LAST_XXX private to fs/namei.c)
interacting with commit
9b012f13c6b671 (ksmbd: fix path resolution in ksmbd_vfs_kern_path_create)
from the ksmbd tree. I have fixed this up as below and can carry as
needed:
diff --git a/fs/smb/server/vfs.c b/fs/smb/server/vfs.c
index da0dbf2209d28b..7e4fffc88dbd75 100644
--- a/fs/smb/server/vfs.c
+++ b/fs/smb/server/vfs.c
@@ -1246,13 +1246,13 @@ struct dentry *ksmbd_vfs_kern_path_create(struct ksmbd_work *work,
struct ksmbd_share_config *share_conf = work->tcon->share_conf;
struct qstr last;
struct dentry *dent;
- int type, err;
+ int err;
/* resolve the name beneath the share root so ".." cannot escape */
CLASS(filename_kernel, filename)(name);
err = vfs_path_parent_lookup(filename, flags | LOOKUP_BENEATH,
- path, &last, &type, &share_conf->vfs_path);
+ path, &last, &share_conf->vfs_path);
if (err)
return ERR_PTR(err);
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
^ permalink raw reply related
* Re: [PATCH v4 0/2] workqueue: Add warnings and check WQ flags usage
From: Tetsuo Handa @ 2026-06-12 13:12 UTC (permalink / raw)
To: Nathan Chancellor, Tejun Heo
Cc: Mark Brown, Linux-Next Mailing List, Linus Torvalds,
Marco Crivellari, linux-kernel, Lai Jiangshan,
Frederic Weisbecker, Sebastian Andrzej Siewior, Michal Hocko,
Breno Leitao
In-Reply-To: <20260610172823.GA804799@ax162>
On 2026/06/11 2:28, Nathan Chancellor wrote:
> FWIW, I sent a patch for the btrfs issue:
>
> https://lore.kernel.org/20260601-btrfs-fix-wq-warning-qgroup-rescan-v1-1-aff9a1128f27@kernel.org/
Then, please immediately add that patch and
https://lkml.kernel.org/r/20260611015545.111157-1-wuyankun@uniontech.com
to the wq tree.
>
> With that applied to next-20260610, I don't see any other instances of
> this workqueue warning on any of my test machines. I do agree that
> enabling warnings prematurely is disruptive for testing and should be
> avoided but it seems like this one is close? That change should be
> applicable to the workqueue tree, it just needs to be taken at this
> point.
>
^ permalink raw reply
* Fixes tags need work in the pmdomain tree
From: Mark Brown @ 2026-06-12 13:39 UTC (permalink / raw)
To: Ulf Hansson; +Cc: linux-kernel, linux-next
[-- Attachment #1: Type: text/plain, Size: 309 bytes --]
In commit
7dbcc2b682501a ("pmdomains: core: fix unused variable warning with !PM_GENERIC_DOMAINS_OF")
Fixes tag
Fixes: 92b69eff8012 ("pmdomain: fix early domain registration")
has these problem(s):
- Subject does not match target commit subject
Just use
git log -1 --format='Fixes: %h ("%s")'
[-- 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