Linux Next

• Thread Index

• Re: [next] arm: boot failed - PC is at cpu_ca15_set_pte_ext
  • From: Naresh Kamboju <naresh.kamboju@xxxxxxxxxx>
• Re: [PATCH v2] Documentation: kvm: Add missing line break in api.rst
  • From: Paolo Bonzini <pbonzini@xxxxxxxxxx>
• Re: linux-next: manual merge of the kunit-next tree with the thunderbolt tree
  • From: Mika Westerberg <mika.westerberg@xxxxxxxxxxxxxxx>
• Re: linux-next: build failure after merge of the pinctrl-renesas tree
  • From: Geert Uytterhoeven <geert@xxxxxxxxxxxxxx>
• Re: [next] arm: boot failed - PC is at cpu_ca15_set_pte_ext
  • From: "Russell King (Oracle)" <linux@xxxxxxxxxxxxxxx>
• Re: [next] arm: boot failed - PC is at cpu_ca15_set_pte_ext
  • From: Naresh Kamboju <naresh.kamboju@xxxxxxxxxx>
• Re: [next] arm: boot failed - PC is at cpu_ca15_set_pte_ext
  • From: Naresh Kamboju <naresh.kamboju@xxxxxxxxxx>
• Re: linux-next: build warning after merge of the bitmap tree
  • From: Yury Norov <yury.norov@xxxxxxxxx>
• linux-next: build warning after merge of the bitmap tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: [next] arm: boot failed - PC is at cpu_ca15_set_pte_ext
  • From: Max Krummenacher <max.oss.09@xxxxxxxxx>
• linux-next: Tree for Apr 20
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: [next] arm: boot failed - PC is at cpu_ca15_set_pte_ext
  • From: Ard Biesheuvel <ardb@xxxxxxxxxx>
• linux-next: build warning after merge of the tty tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: build warning after merge of the drm-misc tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the sysctl tree with the rcu tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the kunit-next tree with the thunderbolt tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: build failure after merge of the pinctrl-renesas tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the pinctrl tree with the devicetree tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• next/pending-fixes baseline: 367 runs, 7 regressions (v5.18-rc3-274-g668a596978074)
  • From: "kernelci.org bot" <bot@xxxxxxxxxxxx>
• linux-next: manual merge of the block tree with Linus' tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• next/pending-fixes build: 209 builds: 2 failed, 207 passed, 6 errors, 6 warnings (v5.18-rc3-274-g668a596978074)
  • From: "kernelci.org bot" <bot@xxxxxxxxxxxx>
• linux-next: manual merge of the arm-soc tree with the samsung-krzk-fixes tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: [next] arm: boot failed - PC is at cpu_ca15_set_pte_ext
  • From: "Russell King (Oracle)" <linux@xxxxxxxxxxxxxxx>
• Re: linux-next: Fixes tag needs some work in the arc-current tree
  • From: Vineet Gupta <vgupta@xxxxxxxxxx>
• next/pending-fixes baseline: 476 runs, 7 regressions (v5.18-rc3-249-g4604e2bc18b6a)
  • From: "kernelci.org bot" <bot@xxxxxxxxxxxx>
• Re: linux-next: build failure after merge of the kvm tree
  • From: Paolo Bonzini <pbonzini@xxxxxxxxxx>
• Re: linux-next: build failure after merge of the kvm tree
  • From: Sean Christopherson <seanjc@xxxxxxxxxx>
• next/master baseline: 455 runs, 167 regressions (next-20220419)
  • From: "kernelci.org bot" <bot@xxxxxxxxxxxx>
• next/pending-fixes build: 208 builds: 2 failed, 206 passed, 6 errors, 6 warnings (v5.18-rc3-249-g4604e2bc18b6a)
  • From: "kernelci.org bot" <bot@xxxxxxxxxxxx>
• next/master build: 172 builds: 6 failed, 166 passed, 20 errors, 67 warnings (next-20220419)
  • From: "kernelci.org bot" <bot@xxxxxxxxxxxx>
• [next] arm: boot failed - PC is at cpu_ca15_set_pte_ext
  • From: Naresh Kamboju <naresh.kamboju@xxxxxxxxxx>
• Re: linux-next: Fixes tag needs some work in the crypto tree
  • From: Giovanni Cabiddu <giovanni.cabiddu@xxxxxxxxx>
• Re: linux-next: Fixes tag needs some work in the imx-mxs tree
  • From: Max Krummenacher <max.krummenacher@xxxxxxxxxxx>
• linux-next: Tree for Apr 19
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: build warning after merge of the tty tree
  • From: Jiri Slaby <jirislaby@xxxxxxxxxx>
• Re: linux-next: build warning after merge of the tty tree
  • From: Jiri Slaby <jirislaby@xxxxxxxxxx>
• Re: linux-next: build warning after merge of the tty tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: build warning after merge of the tty tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: build failure after merge of the kvm tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: build failure after merge of the bitmap tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: build failure after merge of the rcu tree
  • From: "Paul E. McKenney" <paulmck@xxxxxxxxxx>
• linux-next: build failure after merge of the rcu tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: build failure after merge of the bpf-next tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the tip tree with the jc_docs tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the net-next tree with the net tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: Fixes tag needs some work in the crypto tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: Signed-off-by missing for commits in the pm tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: Fixes tag needs some work in the imx-mxs tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: Fixes tag needs some work in the arc-current tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• [next-20220405] powerpc booted with 'bad: scheduling from the idle thread!'
  • From: Abdul Haleem <abdhalee@xxxxxxxxxxxxxxxxxx>
• Re: linux-next: Fixes tag needs some work in the qcom tree
  • From: Konrad Dybcio <konrad.dybcio@xxxxxxxxxxxxxx>
• Re: linux-next: build failure after merge of the amdgpu tree
  • From: Rodrigo Siqueira Jordao <rjordrigo@xxxxxxx>
• Re: linux-next: build failure after merge of the amdgpu tree
  • From: Rodrigo Siqueira Jordao <rjordrigo@xxxxxxx>
• Re: linux-next: build failure after merge of the amdgpu tree
  • From: Alex Deucher <alexdeucher@xxxxxxxxx>
• next/master baseline: 536 runs, 215 regressions (next-20220414)
  • From: "kernelci.org bot" <bot@xxxxxxxxxxxx>
• Re: linux-next: Tree for Apr 14
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: Fixes tag needs some work in the omap-fixes tree
  • From: Tony Lindgren <tony@xxxxxxxxxxx>
• Re: linux-next: manual merge of the drm-misc tree with the drm-misc-fixes tree
  • From: Christian König <christian.koenig@xxxxxxx>
• next/master build: 154 builds: 1 failed, 153 passed, 4 errors, 37 warnings (next-20220414)
  • From: "kernelci.org bot" <bot@xxxxxxxxxxxx>
• linux-next: Tree for Apr 14
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: Fixes tag needs some work in the phy tree
  • From: Vinod Koul <vkoul@xxxxxxxxxx>
• next/pending-fixes baseline: 294 runs, 5 regressions (v5.18-rc2-366-ga3e1163f7eb1a)
  • From: "kernelci.org bot" <bot@xxxxxxxxxxxx>
• Re: mmotm 2022-04-12-21-05 uploaded (fs/btrfs/raid56.o)
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
• Re: mmotm 2022-04-12-21-05 uploaded (ARCH_HAS_NONLEAF_PMD_YOUNG)
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
• Re: mmotm 2022-04-12-21-05 uploaded (ARCH_HAS_NONLEAF_PMD_YOUNG)
  • From: Yu Zhao <yuzhao@xxxxxxxxxx>
• Re: mmotm 2022-04-12-21-05 uploaded (ARCH_HAS_NONLEAF_PMD_YOUNG)
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
• linux-next: manual merge of the efi tree with the tip tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the tip tree with the bpf-next, sysctl trees
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• next/pending-fixes build: 115 builds: 2 failed, 113 passed, 4 errors, 2 warnings (v5.18-rc2-366-ga3e1163f7eb1a)
  • From: "kernelci.org bot" <bot@xxxxxxxxxxxx>
• linux-next: manual merge of the drm-misc tree with the drm-misc-fixes tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: Fixes tag needs some work in the f2fs tree
  • From: Jaegeuk Kim <jaegeuk@xxxxxxxxxx>
• linux-next: Fixes tag needs some work in the f2fs tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: Fixes tag needs some work in the qcom tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: Signed-off-by missing for commit in the dma-mapping tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: Fixes tag needs some work in the phy tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• next/pending-fixes baseline: 377 runs, 6 regressions (v5.18-rc2-321-g174c9b9949da)
  • From: "kernelci.org bot" <bot@xxxxxxxxxxxx>
• RE: lkft kselftest for next-20220412
  • From: "Bird, Tim" <Tim.Bird@xxxxxxxx>
• lkft kselftest for next-20220412
  • From: lkft@xxxxxxxxxx
• next/master baseline: 389 runs, 185 regressions (next-20220413)
  • From: "kernelci.org bot" <bot@xxxxxxxxxxxx>
• next/pending-fixes build: 144 builds: 1 failed, 143 passed, 2 errors, 3 warnings (v5.18-rc2-321-g174c9b9949da)
  • From: "kernelci.org bot" <bot@xxxxxxxxxxxx>
• Re: linux-next: build failure after merge of the amdgpu tree
  • From: Alex Deucher <alexdeucher@xxxxxxxxx>
• lkft kselftest for next-20220411
  • From: lkft@xxxxxxxxxx
• next/master build: 129 builds: 1 failed, 128 passed, 5 errors, 30 warnings (next-20220413)
  • From: "kernelci.org bot" <bot@xxxxxxxxxxxx>
• Re: [next] next-20220412: BUG: Bad page map in process oom_reaper pte
  • From: Naresh Kamboju <naresh.kamboju@xxxxxxxxxx>
• Re: linux-next: build warning after merge of the drm-misc tree
  • From: Christian König <christian.koenig@xxxxxxx>
• Re: linux-next: build warning after merge of the drm-misc tree
  • From: Daniel Vetter <daniel@xxxxxxxx>
• Re: linux-next: Fixes tag needs some work in the omap-fixes tree
  • From: "H. Nikolaus Schaller" <hns@xxxxxxxxxxxxx>
• Re: linux-next: build warning after merge of the akpm-current tree
  • From: Yu Zhao <yuzhao@xxxxxxxxxx>
• linux-next: Tree for Apr 13
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: build warning after merge of the akpm-current tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• mmotm 2022-04-12-21-05 uploaded
  • From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
• linux-next: manual merge of the kvm tree with the kvm-fixes tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: build failure after merge of the amdgpu tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the amdgpu tree with the drm-misc tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: build warnings after merge of the drm-misc tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: build warning after merge of the drm-misc tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the drm-msm tree with Linus' tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: Fixes tag needs some work in the kvm-fixes tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: Fixes tag needs some work in the omap-fixes tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: [next] next-20220412: BUG: Bad page map in process oom_reaper pte
  • From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
• Re: [next] ERROR: modpost: "__udivdi3" [fs/btrfs/btrfs.ko] undefined!
  • From: David Sterba <dsterba@xxxxxxx>
• [next] next-20220412: BUG: Bad page map in process oom_reaper pte
  • From: Naresh Kamboju <naresh.kamboju@xxxxxxxxxx>
• [next] ERROR: modpost: "__udivdi3" [fs/btrfs/btrfs.ko] undefined!
  • From: Naresh Kamboju <naresh.kamboju@xxxxxxxxxx>
• Re: linux-next: manual merge of the dmaengine tree with the dmaengine-fixes tree
  • From: Vinod Koul <vkoul@xxxxxxxxxx>
• linux-next: Tree for Apr 12
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the dmaengine tree with the dmaengine-fixes tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• next/pending-fixes baseline: 431 runs, 7 regressions (v5.18-rc1-608-g6537d9b7dc91)
  • From: "kernelci.org bot" <bot@xxxxxxxxxxxx>
• Re: linux-next: Fixes tags need some work in the kvm-fixes tree
  • From: Heiko Stübner <heiko@xxxxxxxxx>
• next/master baseline: 584 runs, 13 regressions (next-20220411)
  • From: "kernelci.org bot" <bot@xxxxxxxxxxxx>
• linux-next: Fixes tags need some work in the kvm-fixes tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• next/pending-fixes build: 207 builds: 2 failed, 205 passed, 6 errors, 6 warnings (v5.18-rc1-608-g6537d9b7dc91)
  • From: "kernelci.org bot" <bot@xxxxxxxxxxxx>
• next/master build: 218 builds: 9 failed, 209 passed, 23 errors, 38 warnings (next-20220411)
  • From: "kernelci.org bot" <bot@xxxxxxxxxxxx>
• linux-next: Signed-off-by missing for commit in the imx-mxs tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: build warnings after merge of the net tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: Tree for Apr 11
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the akpm-current tree with Linus' tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: Signed-off-by missing for commit in the rockchip tree
  • From: Heiko Stübner <heiko@xxxxxxxxx>
• linux-next: Signed-off-by missing for commit in the rockchip tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• next/master baseline: 420 runs, 10 regressions (next-20220408)
  • From: "kernelci.org bot" <bot@xxxxxxxxxxxx>
• next/pending-fixes baseline: 369 runs, 5 regressions (v5.18-rc1-427-g02f3bd309a78c)
  • From: "kernelci.org bot" <bot@xxxxxxxxxxxx>
• next/master build: 233 builds: 4 failed, 229 passed, 10 errors, 52 warnings (next-20220408)
  • From: "kernelci.org bot" <bot@xxxxxxxxxxxx>
• next/pending-fixes build: 197 builds: 2 failed, 195 passed, 6 errors, 6 warnings (v5.18-rc1-427-g02f3bd309a78c)
  • From: "kernelci.org bot" <bot@xxxxxxxxxxxx>
• lkft kselftest for next-20220408
  • From: lkft@xxxxxxxxxx
• Re: linux-next: please clean up the usb-chipidea-fixes/next trees
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: Fixes tag needs some work in the tip tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: please clean up the usb-chipidea-fixes/next trees
  • From: Peter Chen <peter.chen@xxxxxxxxxx>
• lkft kselftest for next-20220406
  • From: lkft@xxxxxxxxxx
• lkft kselftest for next-20220405
  • From: lkft@xxxxxxxxxx
• Re: linux-next: build failure after merge of the drm-misc tree
  • From: Christian König <christian.koenig@xxxxxxx>
• linux-next: Tree for Apr 8
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the akpm-current tree with the folio tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the akpm-current tree with the folio tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: build failure after merge of the amdgpu tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: build failure after merge of the drm-misc tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: runtime warning after merge of the cel-fixes tree
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: linux-next: runtime warning after merge of the cel-fixes tree
  • From: Chuck Lever III <chuck.lever@xxxxxxxxxx>
• Re: [next] perf build failures: libbpf.c:10946:50: error: format '%li' expects argument of type 'long int *', but argument 4 has type 'size_t *' {aka 'unsigned int *'} [-Werror=format=]
  • From: Andrii Nakryiko <andrii.nakryiko@xxxxxxxxx>
• Re: linux-next: runtime warning after merge of the cel-fixes tree
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: linux-next: runtime warning after merge of the cel-fixes tree
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: linux-next: runtime warning after merge of the cel-fixes tree
  • From: Chuck Lever III <chuck.lever@xxxxxxxxxx>
• Re: linux-next: runtime warning after merge of the cel-fixes tree
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: linux-next: runtime warning after merge of the cel-fixes tree
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: linux-next: runtime warning after merge of the cel-fixes tree
  • From: Chuck Lever III <chuck.lever@xxxxxxxxxx>
• [PATCH v2] Documentation: kvm: Add missing line break in api.rst
  • From: Bagas Sanjaya <bagasdotme@xxxxxxxxx>
• Re: [next] perf build failures: libbpf.c:10946:50: error: format '%li' expects argument of type 'long int *', but argument 4 has type 'size_t *' {aka 'unsigned int *'} [-Werror=format=]
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• [next] perf build failures: libbpf.c:10946:50: error: format '%li' expects argument of type 'long int *', but argument 4 has type 'size_t *' {aka 'unsigned int *'} [-Werror=format=]
  • From: Naresh Kamboju <naresh.kamboju@xxxxxxxxxx>
• linux-next: Tree for Apr 7
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: runtime warning after merge of the cel-fixes tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the kunit-next tree with the net-next tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: Fixes tag needs some work in the kvm-fixes tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: mmotm 2022-04-05-15-54 uploaded [drivers/media/radio/radio-aimslab.ko]
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
• Re: linux-next: manual merge of the rcu tree with the tip tree
  • From: "Paul E. McKenney" <paulmck@xxxxxxxxxx>
• Re: linux-next: build warning after merge of the drm-misc tree
  • From: Marek Vasut <marex@xxxxxxx>
• linux-next: please clean up the usb-chipidea-fixes/next trees
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the rcu tree with the tip tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: [next] riscv: Linux next-20220404 riscv defconfig builds failed.
  • From: Guo Ren <guoren@xxxxxxxxxx>
• next/master baseline: 314 runs, 5 regressions (next-20220406)
  • From: "kernelci.org bot" <bot@xxxxxxxxxxxx>
• Re: linux-next: build failure after merge of the drm-misc tree
  • From: Paul Cercueil <paul@xxxxxxxxxxxxxxx>
• next/pending-fixes baseline: 213 runs, 2 regressions (v5.18-rc1-239-gbd8224be6a15)
  • From: "kernelci.org bot" <bot@xxxxxxxxxxxx>
• next/master build: 231 builds: 3 failed, 228 passed, 6 errors, 39 warnings (next-20220406)
  • From: "kernelci.org bot" <bot@xxxxxxxxxxxx>
• linux-next: Signed-off-by missing for commit in the kbuild tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: build warnings after merge of the drm-misc tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: build warning after merge of the drm-misc tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: [next] riscv: Linux next-20220404 riscv defconfig builds failed.
  • From: Guo Ren <guoren@xxxxxxxxxx>
• linux-next: build warnings after merge of the drm-misc tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: Tree for Apr 6
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: build failure after merge of the drm-misc tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• next/pending-fixes build: 208 builds: 3 failed, 205 passed, 6 errors, 9 warnings (v5.18-rc1-239-gbd8224be6a15)
  • From: "kernelci.org bot" <bot@xxxxxxxxxxxx>
• linux-next: build warning after merge of the drm-misc tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• next/pending-fixes baseline: 207 runs, 5 regressions (v5.18-rc1-178-g95d86c51b643)
  • From: "kernelci.org bot" <bot@xxxxxxxxxxxx>
• Re: linux-next: Signed-off-by missing for commit in the v4l-dvb tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: Signed-off-by missing for commit in the v4l-dvb tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• mmotm 2022-04-05-15-54 uploaded
  • From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
• linux-next: manual merge of the amdgpu tree with the drm-misc tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: please clean up the usb-chipidea-fixes tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: Signed-off-by missing for commit in the v4l-dvb-fixes tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: Signed-off-by missing for commit in the v4l-dvb tree
  • From: Mauro Carvalho Chehab <mchehab@xxxxxxxxxx>
• next/pending-fixes build: 208 builds: 3 failed, 205 passed, 6 errors, 9 warnings (v5.18-rc1-178-g95d86c51b643)
  • From: "kernelci.org bot" <bot@xxxxxxxxxxxx>
• Re: linux-next: Fixes tag needs some work in the modules tree
  • From: Luis Chamberlain <mcgrof@xxxxxxxxxx>
• next/master build: 223 builds: 7 failed, 216 passed, 18 errors, 64 warnings (next-20220405)
  • From: "kernelci.org bot" <bot@xxxxxxxxxxxx>
• Re: [next] riscv: Linux next-20220404 riscv defconfig builds failed.
  • From: Palmer Dabbelt <palmer@xxxxxxxxxxxx>
• next/master baseline: 300 runs, 6 regressions (next-20220405)
  • From: "kernelci.org bot" <bot@xxxxxxxxxxxx>
• Re: linux-next: Fixes tag needs some work in the drivers-x86-fixes tree
  • From: Hans de Goede <hdegoede@xxxxxxxxxx>
• Re: linux-next: manual merge of the rust tree with the kbuild tree
  • From: Miguel Ojeda <miguel.ojeda.sandonis@xxxxxxxxx>
• Duplicate "select GENERIC_IRQ_MULTI_HANDLER"
  • From: Geert Uytterhoeven <geert@xxxxxxxxxxxxxx>
• Re: [next] riscv: Linux next-20220404 riscv defconfig builds failed.
  • From: Guo Ren <guoren@xxxxxxxxxx>
• linux-next: Tree for Apr 5
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the rust tree with the kbuild tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the kunit-next tree with the apparmor tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• mmotm 2022-04-04-17-10 uploaded
  • From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
• linux-next: manual merge of the drm-intel tree with Linus' tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the drm-intel tree with Linus' tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the asm-generic tree with the samsung-krzk-fixes tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the csky tree with Linus' tree
  • From: Palmer Dabbelt <palmer@xxxxxxxxxxxx>
• linux-next: Fixes tag needs some work in the modules tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: Fixes tag needs some work in the scmi tree
  • From: Sudeep Holla <sudeep.holla@xxxxxxx>
• linux-next: Fixes tag needs some work in the scmi tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: Fixes tag needs some work in the drivers-x86-fixes tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• next/master baseline: 257 runs, 3 regressions (next-20220404)
  • From: "kernelci.org bot" <bot@xxxxxxxxxxxx>
• Re: [next] riscv: Linux next-20220404 riscv defconfig builds failed.
  • From: Nathan Chancellor <nathan@xxxxxxxxxx>
• next/pending-fixes baseline: 210 runs, 4 regressions (v5.18-rc1-107-g56ad09fc9d717)
  • From: "kernelci.org bot" <bot@xxxxxxxxxxxx>
• next/master build: 223 builds: 12 failed, 211 passed, 23 errors, 78 warnings (next-20220404)
  • From: "kernelci.org bot" <bot@xxxxxxxxxxxx>
• next/pending-fixes build: 207 builds: 3 failed, 204 passed, 6 errors, 9 warnings (v5.18-rc1-107-g56ad09fc9d717)
  • From: "kernelci.org bot" <bot@xxxxxxxxxxxx>
• Re: [next] riscv: Linux next-20220404 riscv defconfig builds failed.
  • From: Guo Ren <guoren@xxxxxxxxxx>
• [next] riscv: Linux next-20220404 riscv defconfig builds failed.
  • From: Naresh Kamboju <naresh.kamboju@xxxxxxxxxx>
• Re: linux-next: build failure after merge of the sysctl tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: build warning after merge of the spi-fixes tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: build warnings after merge of the tip tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: Tree for Apr 4
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: build failure after merge of the sysctl tree
  • From: Luis Chamberlain <mcgrof@xxxxxxxxxx>
• Re: linux-next: build failure after merge of the sysctl tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the csky tree with Linus' tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the csky tree with Linus' tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the kbuild tree with Linus' tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: mmotm 2022-03-31-20-37 uploaded (drivers/net/ethernet/fungible/funcore/fun_dev.o)
  • From: Dimitris Michailidis <d.michailidis@xxxxxxxxxxxx>
• Re: mmotm 2022-03-31-20-37 uploaded (drivers/net/ethernet/fungible/funcore/fun_dev.o)
  • From: Jakub Kicinski <kuba@xxxxxxxxxx>
• Re: linux-next: manual merge of the device-mapper tree with the block tree
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• RE: mmotm 2022-03-30-13-01 uploaded (drivers/platform/x86/amd-pmc.o)
  • From: "Limonciello, Mario" <Mario.Limonciello@xxxxxxx>
• Re: mmotm 2022-03-30-13-01 uploaded (drivers/platform/x86/amd-pmc.o)
  • From: Hans de Goede <hdegoede@xxxxxxxxxx>
• lkft kselftest for next-20220401
  • From: lkft@xxxxxxxxxx
• next/master baseline: 455 runs, 15 regressions (next-20220401)
  • From: "kernelci.org bot" <bot@xxxxxxxxxxxx>
• next/pending-fixes baseline: 400 runs, 20 regressions (v5.17-13747-gaeb9fed350ee)
  • From: "kernelci.org bot" <bot@xxxxxxxxxxxx>
• [next] arm64: sdei.c:124:33: error: 'sdei_shadow_call_stack_normal_ptr' undeclared
  • From: Naresh Kamboju <naresh.kamboju@xxxxxxxxxx>
• [next] arm64: builds failed - stacktrace.c:(.text+0x55c): undefined reference to `arch_stack_walk_shadow'
  • From: Naresh Kamboju <naresh.kamboju@xxxxxxxxxx>
• next/master build: 224 builds: 12 failed, 212 passed, 26 errors, 78 warnings (next-20220401)
  • From: "kernelci.org bot" <bot@xxxxxxxxxxxx>
• next/pending-fixes build: 209 builds: 4 failed, 205 passed, 7 errors, 10 warnings (v5.17-13747-gaeb9fed350ee)
  • From: "kernelci.org bot" <bot@xxxxxxxxxxxx>
• Re: linux-next: manual merge of the device-mapper tree with the block tree
  • From: Christoph Hellwig <hch@xxxxxx>
• Re: mmotm 2022-03-31-20-37 uploaded (drivers/net/ethernet/fungible/funcore/fun_dev.o)
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
• mmotm 2022-03-31-20-37 uploaded
  • From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
• Re: linux-next: build warning after merge of the risc-v tree
  • From: Palmer Dabbelt <palmer@xxxxxxxxxxx>
• linux-next: Tree for Apr 1
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: build warning after merge of the risc-v tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: [PATCH] Documentation: riscv: remove non-existent document from table of contents
  • From: Palmer Dabbelt <palmer@xxxxxxxxxxx>
• Re: linux-next: build warning after merge of the risc-v tree
  • From: Palmer Dabbelt <palmer@xxxxxxxxxxx>
• Re: mmotm 2022-03-30-13-01 uploaded (kernel/sched/ and sysctls)
  • From: Luis Chamberlain <mcgrof@xxxxxxxxxx>
• next/pending-fixes baseline: 321 runs, 12 regressions (v5.17-13559-g412036f22f46)
  • From: "kernelci.org bot" <bot@xxxxxxxxxxxx>
• linux-next: Fixes tag needs some work in the chrome-platform tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: Fixes tag needs some work in the dma-mapping tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• next/pending-fixes build: 210 builds: 4 failed, 206 passed, 7 errors, 278 warnings (v5.17-13559-g412036f22f46)
  • From: "kernelci.org bot" <bot@xxxxxxxxxxxx>
• Re: kselftest: net: tls: hangs
  • From: Jakub Kicinski <kuba@xxxxxxxxxx>
• RE: mmotm 2022-03-30-13-01 uploaded (drivers/platform/x86/amd-pmc.o)
  • From: "Limonciello, Mario" <Mario.Limonciello@xxxxxxx>
• Re: mmotm 2022-03-30-13-01 uploaded (drivers/platform/x86/amd-pmc.o)
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
• Re: mmotm 2022-03-30-13-01 uploaded (DWARF error: could not find abbrev number 74)
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
• Re: [next ] x86: Assembler messages: Error: invalid operands (*UND* and .data..percpu sections) for `+'
  • From: Paolo Bonzini <pbonzini@xxxxxxxxxx>
• [next ] x86: Assembler messages: Error: invalid operands (*UND* and .data..percpu sections) for `+'
  • From: Naresh Kamboju <naresh.kamboju@xxxxxxxxxx>
• Re: kselftest: net: tls: hangs
  • From: Naresh Kamboju <naresh.kamboju@xxxxxxxxxx>
• Re: mmotm 2022-03-30-13-01 uploaded (kernel/sched/ and sysctls)
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
• linux-next: build failure after merge of the akpm-current tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: Tree for Mar 31
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• 答复: linux-next: manual merge of the kvm tree with Linus' tree
  • From: "Li,Rongqing" <lirongqing@xxxxxxxxx>
• linux-next: manual merge of the kvm tree with Linus' tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the device-mapper tree with the block tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the xfs tree with Linus' tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: [EXTERNAL] linux-next: Signed-off-bys missing for commits in the kvm tree
  • From: David Woodhouse <dwmw2@xxxxxxxxxxxxx>
• linux-next: Signed-off-bys missing for commits in the kvm tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• mmotm 2022-03-30-13-01 uploaded
  • From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
• Re: linux-next: build failure after merge of the sysctl tree
  • From: Luis Chamberlain <mcgrof@xxxxxxxxxx>
• next/master baseline: 506 runs, 20 regressions (next-20220330)
  • From: "kernelci.org bot" <bot@xxxxxxxxxxxx>
• next/master build: 220 builds: 5 failed, 215 passed, 8 errors, 64 warnings (next-20220330)
  • From: "kernelci.org bot" <bot@xxxxxxxxxxxx>
• next/pending-fixes baseline: 301 runs, 8 regressions (v5.17-13070-gc7e54cdeb141)
  • From: "kernelci.org bot" <bot@xxxxxxxxxxxx>
• next/pending-fixes build: 206 builds: 3 failed, 203 passed, 6 errors, 273 warnings (v5.17-13070-gc7e54cdeb141)
  • From: "kernelci.org bot" <bot@xxxxxxxxxxxx>
• Re: linux-next: Signed-off-by missing for commit in the block tree
  • From: Christoph Hellwig <hch@xxxxxx>
• linux-next: Tree for Mar 30
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: build failure after merge of the sysctl tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the device-mapper tree with Linus' tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the clk tree with Linus' tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: Signed-off-by missing for commit in the block tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: kselftest: net: tls: hangs
  • From: Jakub Kicinski <kuba@xxxxxxxxxx>
• Re: kselftest: net: tls: hangs
  • From: Naresh Kamboju <naresh.kamboju@xxxxxxxxxx>
• Re: linux-next: build warning after merge of the risc-v tree
  • From: Palmer Dabbelt <palmer@xxxxxxxxxxx>
• next/master baseline: 574 runs, 28 regressions (next-20220329)
  • From: "kernelci.org bot" <bot@xxxxxxxxxxxx>
• Re: kselftest: net: tls: hangs
  • From: Naresh Kamboju <naresh.kamboju@xxxxxxxxxx>
• next/master build: 220 builds: 5 failed, 215 passed, 9 errors, 64 warnings (next-20220329)
  • From: "kernelci.org bot" <bot@xxxxxxxxxxxx>
• [PATCH] Documentation: riscv: remove non-existent document from table of contents
  • From: Bagas Sanjaya <bagasdotme@xxxxxxxxx>
• next/pending-fixes baseline: 329 runs, 5 regressions (v5.17-12935-gafa5b5041c02)
  • From: "kernelci.org bot" <bot@xxxxxxxxxxxx>
• Re: linux-next: build warnings after merge of the akpm-current tree
  • From: Hugh Dickins <hughd@xxxxxxxxxx>
• linux-next: Tree for Mar 29
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: build warning after merge of the risc-v tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• next/pending-fixes build: 209 builds: 4 failed, 205 passed, 7 errors, 278 warnings (v5.17-12935-gafa5b5041c02)
  • From: "kernelci.org bot" <bot@xxxxxxxxxxxx>
• next/pending-fixes baseline: 361 runs, 12 regressions (v5.17-11526-gd877adea8dd9)
  • From: "kernelci.org bot" <bot@xxxxxxxxxxxx>
• next/master baseline: 454 runs, 19 regressions (next-20220328)
  • From: "kernelci.org bot" <bot@xxxxxxxxxxxx>
• Re: linux-next: build warnings after merge of the akpm-current tree
  • From: Matthew Wilcox <willy@xxxxxxxxxxxxx>
• Re: s390 defconfig fails to build after 4afeb670710efa5cd5ed8b1d9f2d22d6ce332bcc
  • From: Vasily Gorbik <gor@xxxxxxxxxxxxx>
• Re: linux-next: build warnings after merge of the akpm-current tree
  • From: Matthew Wilcox <willy@xxxxxxxxxxxxx>
• next/master build: 223 builds: 8 failed, 215 passed, 23 errors, 56 warnings (next-20220328)
  • From: "kernelci.org bot" <bot@xxxxxxxxxxxx>
• next/pending-fixes build: 208 builds: 3 failed, 205 passed, 6 errors, 277 warnings (v5.17-11526-gd877adea8dd9)
  • From: "kernelci.org bot" <bot@xxxxxxxxxxxx>
• Re: s390 defconfig fails to build after 4afeb670710efa5cd5ed8b1d9f2d22d6ce332bcc
  • From: Nathan Chancellor <nathan@xxxxxxxxxx>
• linux-next: Fixes tag needs some work in the block tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: Fixes tag needs some work in the jc_docs tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• [PATCH] mm/munlock: remove fields to fix htmldocs warnings
  • From: Hugh Dickins <hughd@xxxxxxxxxx>
• Re: linux-next: build warnings after merge of the akpm-current tree
  • From: Hugh Dickins <hughd@xxxxxxxxxx>
• s390 defconfig fails to build after 4afeb670710efa5cd5ed8b1d9f2d22d6ce332bcc
  • From: Nathan Chancellor <nathan@xxxxxxxxxx>
• Re: linux-next: build warning after merge of the drm-misc tree
  • From: Andrey Grodzovsky <andrey.grodzovsky@xxxxxxx>
• linux-next: Tree for Mar 28
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: build warning after merge of the drm-misc tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: build failure in Linus' tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the cifs tree with Linus' tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: build failure in Linus' tree
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• Re: linux-next: build failure in Linus' tree
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• Re: linux-next: Signed-off-by missing for commit in the kspp-gustavo tree
  • From: "Gustavo A. R. Silva" <gustavo@xxxxxxxxxxxxxx>
• linux-next: build failure in Linus' tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: Signed-off-by missing for commit in the kspp-gustavo tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: Signed-off-by missing for commit in the gfs2 tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: Fixes tag needs some work in the watchdog tree
  • From: Wim Van Sebroeck <wim@xxxxxxxxx>
• Re: kselftest: net: tls: hangs
  • From: Shuah Khan <skhan@xxxxxxxxxxxxxxxxxxx>
• Re: kselftest: net: tls: hangs
  • From: Jakub Kicinski <kuba@xxxxxxxxxx>
• Re: kselftest: net: tls: hangs
  • From: Shuah Khan <skhan@xxxxxxxxxxxxxxxxxxx>
• Re: next: BUG: sleeping function called from invalid context at block/blk-sysfs.c:766
  • From: Eric Biggers <ebiggers@xxxxxxxxxx>
• next/pending-fixes baseline: 294 runs, 12 regressions (v5.17-7667-gf25e53282ab9)
  • From: "kernelci.org bot" <bot@xxxxxxxxxxxx>
• next/master build: 159 builds: 4 failed, 155 passed, 7 errors, 15 warnings (next-20220325)
  • From: "kernelci.org bot" <bot@xxxxxxxxxxxx>
• next/pending-fixes build: 135 builds: 2 failed, 133 passed, 3 errors, 2 warnings (v5.17-7667-gf25e53282ab9)
  • From: "kernelci.org bot" <bot@xxxxxxxxxxxx>
• Re: linux-next: build warning after merge of the amdgpu tree
  • From: Christian König <christian.koenig@xxxxxxx>
• linux-next: build warning after merge of the amdgpu tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• kselftest: net: tls: hangs
  • From: Naresh Kamboju <naresh.kamboju@xxxxxxxxxx>
• linux-next: Tree for Mar 25
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• [PATCH] docs: kernel_abi.py: add sphinx build dependencies
  • From: Mauro Carvalho Chehab <mchehab@xxxxxxxxxx>
• Re: linux-next: build warnings after merge of the drivers-x86 tree
  • From: Mauro Carvalho Chehab <mchehab@xxxxxxxxxx>
• Re: linux-next: build warnings after merge of the drivers-x86 tree
  • From: Mauro Carvalho Chehab <mchehab@xxxxxxxxxx>
• linux-next: manual merge of the btrfs tree with the btrfs-fixes tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: Upcoming merge conflict between s390 and kvm / kvms390 trees
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the userns tree with the asm-generic tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the h8300 tree with the asm-generic tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: build warnings after merge of the drivers-x86 tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• next/master baseline: 446 runs, 6 regressions (next-20220324)
  • From: "kernelci.org bot" <bot@xxxxxxxxxxxx>
• Re: linux-next: build warnings after merge of the drivers-x86 tree
  • From: Hans de Goede <hdegoede@xxxxxxxxxx>
• Re: linux-next: build warnings after merge of the drivers-x86 tree
  • From: Hans de Goede <hdegoede@xxxxxxxxxx>
• next/master build: 223 builds: 10 failed, 213 passed, 26 errors, 67 warnings (next-20220324)
  • From: "kernelci.org bot" <bot@xxxxxxxxxxxx>
• Re: linux-next: build warnings after merge of the drivers-x86 tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• next: BUG: sleeping function called from invalid context at block/blk-sysfs.c:766
  • From: Naresh Kamboju <naresh.kamboju@xxxxxxxxxx>
• Re: linux-next: build warnings after merge of the drivers-x86 tree
  • From: Hans de Goede <hdegoede@xxxxxxxxxx>
• linux-next: Tree for Mar 24
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: build warnings after merge of the drivers-x86 tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the vfs tree with the arm64 tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: build warnings after merge of the akpm-current tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• next/pending-fixes baseline: 252 runs, 9 regressions (v5.17-2918-g4fb3edfb1fc4)
  • From: "kernelci.org bot" <bot@xxxxxxxxxxxx>
• Re: linux-next: manual merge of the folio tree with the drm-intel tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• next/pending-fixes build: 133 builds: 2 failed, 131 passed, 3 errors, 4 warnings (v5.17-2918-g4fb3edfb1fc4)
  • From: "kernelci.org bot" <bot@xxxxxxxxxxxx>
• Re: linux-next: manual merge of the folio tree with the nfs tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the folio tree with the fscache tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the folio tree with the fscache tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the folio tree with the ubifs-fixes tree
  • From: Richard Weinberger <richard@xxxxxx>
• Re: linux-next: manual merge of the akpm-current tree with the asm-generic tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the folio tree with the asm-generic tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the folio tree with the ubifs-fixes tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: [PATCH 1/2] drivers/nvdimm: Fix build failure when CONFIG_PERF_EVENTS is not set
  • From: kajoljain <kjain@xxxxxxxxxxxxx>
• Re: [PATCH 2/2] powerpc/papr_scm: Fix build failure when CONFIG_PERF_EVENTS is not set
  • From: kajoljain <kjain@xxxxxxxxxxxxx>
• Re: [PATCH 2/2] powerpc/papr_scm: Fix build failure when CONFIG_PERF_EVENTS is not set
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• next/master baseline: 162 runs, 1 regressions (next-20220323)
  • From: "kernelci.org bot" <bot@xxxxxxxxxxxx>
• next/master build: 155 builds: 6 failed, 149 passed, 12 errors, 62 warnings (next-20220323)
  • From: "kernelci.org bot" <bot@xxxxxxxxxxxx>
• Re: [PATCH 2/2] powerpc/papr_scm: Fix build failure when CONFIG_PERF_EVENTS is not set
  • From: Michael Ellerman <mpe@xxxxxxxxxxxxxx>
• linux-next: Tree for Mar 23
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: [PATCH 2/2] powerpc/papr_scm: Fix build failure when CONFIG_PERF_EVENTS is not set
  • From: Vaibhav Jain <vaibhav@xxxxxxxxxxxxx>
• Re: linux-next: build warnings after merge of the tip tree
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• next/pending-fixes baseline: 182 runs, 7 regressions (v5.17-2275-g6bcc7ba3ca32)
  • From: "kernelci.org bot" <bot@xxxxxxxxxxxx>
• Re: linux-next: build warnings after merge of the tip tree
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: linux-next: build warnings after merge of the tip tree
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• Re: linux-next: Fixes tag needs some work in the block tree
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: linux-next: manual merge of the mfd tree with the arm-soc tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• next/pending-fixes build: 125 builds: 1 failed, 124 passed, 4 errors, 1 warning (v5.17-2275-g6bcc7ba3ca32)
  • From: "kernelci.org bot" <bot@xxxxxxxxxxxx>
• Re: linux-next: build warnings after merge of the tip tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the risc-v tree with Linus' tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the spi tree with the arm-soc tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: build warnings after merge of the tip tree
  • From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
• linux-next: Fixes tag needs some work in the block tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the parisc-hd tree with the asm-generic tree
  • From: Helge Deller <deller@xxxxxx>
• Re: linux-next: manual merge of the parisc-hd tree with the asm-generic tree
  • From: Arnd Bergmann <arnd@xxxxxxxx>
• next/master baseline: 221 runs, 11 regressions (next-20220322)
  • From: "kernelci.org bot" <bot@xxxxxxxxxxxx>
• Re: [PATCH 2/2] powerpc/papr_scm: Fix build failure when CONFIG_PERF_EVENTS is not set
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: linux-next: build warnings after merge of the tip tree
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: linux-next: build warnings after merge of the tip tree
  • From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
• Re: linux-next: build warnings after merge of the tip tree
  • From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
• Re: linux-next: build warnings after merge of the tip tree
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: linux-next: build warnings after merge of the tip tree
  • From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
• Re: [PATCH 2/2] powerpc/papr_scm: Fix build failure when CONFIG_PERF_EVENTS is not set
  • From: kajoljain <kjain@xxxxxxxxxxxxx>
• Re: [PATCH 2/2] powerpc/papr_scm: Fix build failure when CONFIG_PERF_EVENTS is not set
  • From: kajoljain <kjain@xxxxxxxxxxxxx>
• Re: linux-next: build warnings after merge of the tip tree
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• Re: linux-next: build warnings after merge of the tip tree
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• Re: linux-next: build warnings after merge of the tip tree
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: linux-next: build warnings after merge of the tip tree
  • From: Mark Rutland <mark.rutland@xxxxxxx>
• Re: linux-next: build warnings after merge of the tip tree
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: linux-next: build warnings after merge of the tip tree
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• Re: linux-next: manual merge of the devicetree tree with the mfd tree
  • From: Rob Herring <robherring2@xxxxxxxxx>
• Re: linux-next: build warnings after merge of the tip tree
  • From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
• Re: linux-next: build warnings after merge of the tip tree
  • From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
• next/pending-fixes baseline: 333 runs, 7 regressions (v5.17-1379-g27610c0a0ca2)
  • From: "kernelci.org bot" <bot@xxxxxxxxxxxx>
• Re: linux-next: build warnings after merge of the tip tree
  • From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
• Re: linux-next: build warnings after merge of the tip tree
  • From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
• linux-next: Tree for Mar 22
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: build warnings after merge of the tip tree
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• Re: linux-next: manual merge of the char-misc tree with the net-next tree
  • From: Geert Uytterhoeven <geert@xxxxxxxxxxxxxx>
• linux-next: manual merge of the akpm-current tree with the folio tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• next/pending-fixes build: 210 builds: 4 failed, 206 passed, 4 errors, 6 warnings (v5.17-1379-g27610c0a0ca2)
  • From: "kernelci.org bot" <bot@xxxxxxxxxxxx>
• Re: linux-next: build warnings after merge of the tip tree
  • From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
• Re: linux-next: build warnings after merge of the tip tree
  • From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
• Re: linux-next: build warnings after merge of the tip tree
  • From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
• Re: linux-next: manual merge of the parisc-hd tree with the asm-generic tree
  • From: Helge Deller <deller@xxxxxx>
• Re: linux-next: manual merge of the devicetree tree with the mfd tree
  • From: Lee Jones <lee.jones@xxxxxxxxxx>
• Re: linux-next: build failure after merge of the net-next tree
  • From: Saeed Mahameed <saeed@xxxxxxxxxx>
• Re: linux-next: build warnings after merge of the tip tree
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• Re: linux-next: build warnings after merge of the tip tree
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• Re: linux-next: build warnings after merge of the tip tree
  • From: Alexei Starovoitov <alexei.starovoitov@xxxxxxxxx>
• Re: linux-next: build warnings after merge of the tip tree
  • From: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
• linux-next: build warnings after merge of the tip tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the devicetree tree with the mfd tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: [PATCH 1/2] drivers/nvdimm: Fix build failure when CONFIG_PERF_EVENTS is not set
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• next/master baseline: 277 runs, 9 regressions (next-20220321)
  • From: "kernelci.org bot" <bot@xxxxxxxxxxxx>
• Re: [PATCH 2/2] powerpc/papr_scm: Fix build failure when CONFIG_PERF_EVENTS is not set
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: linux-next: manual merge of the parisc-hd tree with the asm-generic tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: build warnings after merge of the tip tree
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: linux-next: build failure after merge of the net-next tree
  • From: Jakub Kicinski <kuba@xxxxxxxxxx>
• Re: linux-next: build warnings after merge of the tip tree
  • From: Alexei Starovoitov <alexei.starovoitov@xxxxxxxxx>
• Re: linux-next: build warnings after merge of the tip tree
  • From: Alexei Starovoitov <alexei.starovoitov@xxxxxxxxx>
• Re: linux-next: build warnings after merge of the tip tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• next/master build: 223 builds: 11 failed, 212 passed, 18 errors, 89 warnings (next-20220321)
  • From: "kernelci.org bot" <bot@xxxxxxxxxxxx>
• Re: linux-next: build warnings after merge of the tip tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: [PATCH 2/2] powerpc/papr_scm: Fix build failure when CONFIG_PERF_EVENTS is not set
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: [syzbot] linux-next test error: WARNING in __napi_schedule
  • From: Jakub Kicinski <kuba@xxxxxxxxxx>
• Re: linux-next: build warnings after merge of the tip tree
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: linux-next: build warnings after merge of the tip tree
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• Re: linux-next: build warnings after merge of the tip tree
  • From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
• next/pending-fixes baseline: 226 runs, 3 regressions (v5.17-100-gfb4e0eea8056)
  • From: "kernelci.org bot" <bot@xxxxxxxxxxxx>
• Re: linux-next: build warnings after merge of the tip tree
  • From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
• Re: linux-next: build warnings after merge of the tip tree
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: linux-next: build warnings after merge of the tip tree
  • From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
• Re: linux-next: build warnings after merge of the tip tree
  • From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
• Re: linux-next: build warnings after merge of the tip tree
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: linux-next: build warnings after merge of the tip tree
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• Re: linux-next: build warnings after merge of the tip tree
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: linux-next: build warnings after merge of the tip tree
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: linux-next: build warnings after merge of the tip tree
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: linux-next: build warnings after merge of the tip tree
  • From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
• Re: linux-next: build warnings after merge of the tip tree
  • From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
• Re: linux-next: build warnings after merge of the tip tree
  • From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
• Re: linux-next: build warnings after merge of the tip tree
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: linux-next: Fixes tag needs some work in the irqchip tree
  • From: Marc Zyngier <maz@xxxxxxxxxx>
• Re: linux-next: build warnings after merge of the tip tree
  • From: Mark Rutland <mark.rutland@xxxxxxx>
• Re: linux-next: build warnings after merge of the tip tree
  • From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
• next/pending-fixes build: 190 builds: 4 failed, 186 passed, 4 errors, 4 warnings (v5.17-100-gfb4e0eea8056)
  • From: "kernelci.org bot" <bot@xxxxxxxxxxxx>
• Re: linux-next: build warnings after merge of the tip tree
  • From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
• linux-next: Signed-off-by missing for commit in the kvm tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: Fixes tag needs some work in the irqchip tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: build warnings after merge of the tip tree
  • From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
• Re: linux-next: build warnings after merge of the tip tree
  • From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
• linux-next: Tree for Mar 21
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: run time failure after merge of the bpf-next tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: build failure after merge of the net-next tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the rust tree with the bpf-next tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: build warnings after merge of the tip tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the block tree with Linus' tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the bpf-next tree with the arm tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: the merge window is open
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: Fixes tag needs some work in the watchdog tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• [syzbot] linux-next test error: WARNING in __napi_schedule
  • From: syzbot <syzbot+6f21ac9e27fca7e97623@xxxxxxxxxxxxxxxxxxxxxxxxx>
• next/master build: 223 builds: 11 failed, 212 passed (next-20220318)
  • From: "kernelci.org bot" <bot@xxxxxxxxxxxx>
• next/pending-fixes build: 163 builds: 3 failed, 160 passed (v5.17-rc8-149-g382d8f4c46c1f)
  • From: "kernelci.org bot" <bot@xxxxxxxxxxxx>
• next/master build: 192 builds: 11 failed, 181 passed, 12 errors, 6 warnings (next-20220317)
  • From: "kernelci.org bot" <bot@xxxxxxxxxxxx>
• RE: linux-next: Fixes tag needs some work in the spi tree
  • From: Biju Das <biju.das.jz@xxxxxxxxxxxxxx>
• Re: linux-next: Fixes tag needs some work in the spi tree
  • From: Mark Brown <broonie@xxxxxxxxxx>
• [PATCH 2/2] powerpc/papr_scm: Fix build failure when CONFIG_PERF_EVENTS is not set
  • From: Kajol Jain <kjain@xxxxxxxxxxxxx>
• [PATCH 1/2] drivers/nvdimm: Fix build failure when CONFIG_PERF_EVENTS is not set
  • From: Kajol Jain <kjain@xxxxxxxxxxxxx>
• linux-next: Tree for Mar 18
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the usb tree with the xilinx tree
  • From: Michal Simek <michal.simek@xxxxxxxxxx>
• Re: linux-next: manual merge of the qcom tree with the imx-mxs tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the usb tree with the xilinx tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the usb tree with the qcom tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: build warning after merge of the pinctrl tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: build warning after merge of the spi-fixes tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the tegra tree with the qcom tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• RE: linux-next: Fixes tag needs some work in the spi tree
  • From: Biju Das <biju.das.jz@xxxxxxxxxxxxxx>
• Re: mmotm 2022-03-16-17-42 uploaded (uml sub-x86_64, sched/fair, RCU)
  • From: Sachin Sant <sachinp@xxxxxxxxxxxxx>
• Re: mmotm 2022-03-16-17-42 uploaded (uml sub-x86_64, sched/fair, RCU)
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
• RE: linux-next: Fixes tag needs some work in the f2fs tree
  • From: 常凤楠 <changfengnan@xxxxxxxx>
• Re: linux-next: manual merge of the drm tree with the drm-misc-fixes tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the drm tree with the drm-misc-fixes tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: mmotm 2022-03-16-17-42 uploaded (uml sub-x86_64, sched/fair, RCU)
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
• Re: mmotm 2022-03-16-17-42 uploaded (uml sub-x86_64, sched/fair, RCU)
  • From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
• linux-next: Fixes tag needs some work in the spi tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: Fixes tag needs some work in the bpf-next tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: Fixes tag needs some work in the f2fs tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: [powerpc] 5.17-rc8-next-20220317 build break kernel/sched/fair.o
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
• Re: mmotm 2022-03-16-17-42 uploaded (uml sub-x86_64, sched/fair, RCU)
  • From: "Paul E. McKenney" <paulmck@xxxxxxxxxx>
• [powerpc] 5.17-rc8-next-20220317 build break kernel/sched/fair.o
  • From: Sachin Sant <sachinp@xxxxxxxxxxxxx>
• linux-next: Tree for Mar 17
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: build failure after merge of the kspp tree
  • From: Marc Zyngier <maz@xxxxxxxxxx>
• next/pending-fixes baseline: 261 runs, 10 regressions (v5.17-rc8-133-gcdf39fcb6bec)
  • From: "kernelci.org bot" <bot@xxxxxxxxxxxx>
• Re: linux-next: manual merge of the rust tree with the kbuild tree
  • From: Miguel Ojeda <miguel.ojeda.sandonis@xxxxxxxxx>
• Re: mmotm 2022-03-16-17-42 uploaded (uml sub-x86_64, sched/fair, RCU)
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
• Re: mmotm 2022-03-16-17-42 uploaded (drivers/iio/afe/iio-rescale.o)
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
• Re: mmotm 2022-03-16-17-42 uploaded (uml sub-x86_64, sched/fair, RCU)
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
• Re: mmotm 2022-03-16-17-42 uploaded (drivers/pinctrl/nuvoton/pinctrl-wpcm450.c)
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
• Re: mmotm 2022-03-16-17-42 uploaded (uml sub-x86_64, sched/fair, RCU)
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
• linux-next: manual merge of the rust tree with the kbuild tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• next/pending-fixes build: 175 builds: 5 failed, 170 passed, 7 errors, 5 warnings (v5.17-rc8-133-gcdf39fcb6bec)
  • From: "kernelci.org bot" <bot@xxxxxxxxxxxx>
• Re: mmotm 2022-03-16-17-42 uploaded (uml sub-x86_64, sched/fair, RCU)
  • From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
• Re: linux-next: build failure after merge of the kspp tree
  • From: Linus Walleij <linus.walleij@xxxxxxxxxx>
• mmotm 2022-03-16-17-42 uploaded
  • From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
• next/master baseline: 260 runs, 18 regressions (next-20220316)
  • From: "kernelci.org bot" <bot@xxxxxxxxxxxx>
• Re: linux-next: build failure after merge of the userns tree
  • From: "Eric W. Biederman" <ebiederm@xxxxxxxxxxxx>
• next/master build: 180 builds: 13 failed, 167 passed, 32 errors, 77 warnings (next-20220316)
  • From: "kernelci.org bot" <bot@xxxxxxxxxxxx>
• Re: linux-next: build failure after merge of the kspp tree (in pinctrl-npcm7xx)
  • From: Jonathan Neuschäfer <j.neuschaefer@xxxxxxx>
• linux-next: Tree for Mar 16
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: build failure after merge of the kspp tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: build failure after merge of the userns tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• next/pending-fixes baseline: 381 runs, 13 regressions (v5.17-rc8-122-ge6f79dd905ae)
  • From: "kernelci.org bot" <bot@xxxxxxxxxxxx>
• Re: linux-next: manual merge of the ftrace tree with the nfsd tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• next/pending-fixes build: 212 builds: 6 failed, 206 passed, 7 errors, 6 warnings (v5.17-rc8-122-ge6f79dd905ae)
  • From: "kernelci.org bot" <bot@xxxxxxxxxxxx>
• Re: linux-next: manual merge of the folio tree with the ubifs-fixes tree
  • From: Zhihao Cheng <chengzhihao1@xxxxxxxxxx>
• Re: linux-next: manual merge of the sysctl tree with the tip tree
  • From: Luis Chamberlain <mcgrof@xxxxxxxxxx>
• next/master baseline: 306 runs, 18 regressions (next-20220315)
  • From: "kernelci.org bot" <bot@xxxxxxxxxxxx>
• Re: linux-next: manual merge of the sysctl tree with the tip tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the sysctl tree with the tip tree
  • From: Luis Chamberlain <mcgrof@xxxxxxxxxx>
• next/master build: 198 builds: 17 failed, 181 passed, 31 errors, 53 warnings (next-20220315)
  • From: "kernelci.org bot" <bot@xxxxxxxxxxxx>
• Re: linux-next: manual merge of the folio tree with the ext4 tree
  • From: "Theodore Ts'o" <tytso@xxxxxxx>
• Re: linux-next: manual merge of the ftrace tree with the nfsd tree
  • From: Chuck Lever III <chuck.lever@xxxxxxxxxx>
• Re: linux-next: manual merge of the ftrace tree with the nfsd tree
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: linux-next: manual merge of the nvdimm tree with the powerpc tree
  • From: Vaibhav Jain <vaibhav@xxxxxxxxxxxxx>
• Re: linux-next: manual merge of the nvdimm tree with the powerpc tree
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: linux-next: build failure after merge of the folio tree
  • From: Matthew Wilcox <willy@xxxxxxxxxxxxx>
• Re: linux-next: manual merge of the ftrace tree with the nfsd tree
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: linux-next: manual merge of the nvdimm tree with the powerpc tree
  • From: kajoljain <kjain@xxxxxxxxxxxxx>
• Re: linux-next: manual merge of the ftrace tree with the nfsd tree
  • From: Chuck Lever III <chuck.lever@xxxxxxxxxx>
• Re: linux-next: build failure after merge of the net-next tree
  • From: Vladimir Oltean <vladimir.oltean@xxxxxxx>
• linux-next: Tree for Mar 15
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the folio tree with the ext4 tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the akpm-current tree with the bpf-next tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: build failure after merge of the net-next tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the folio tree with the ext4 tree
  • From: Jan Kara <jack@xxxxxxx>
• Re: linux-next: manual merge of the nvdimm tree with the powerpc tree
  • From: Michael Ellerman <mpe@xxxxxxxxxxxxxx>
• linux-next: manual merge of the kspp tree with Linus' tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: build failure after merge of the tip tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: build failure after merge of the folio tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the folio tree with the ubifs-fixes tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the folio tree with the nfs tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the folio tree with the ext4 tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the folio tree with the erofs tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the folio tree with the fscache tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the folio tree with the fscache tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: build failure after merge of the tip tree
  • From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
• linux-next: manual merge of the sysctl tree with the tip tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: build failure after merge of the tip tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the nvdimm tree with the block tree
  • From: Christoph Hellwig <hch@xxxxxx>
• linux-next: manual merge of the nvdimm tree with the block tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the nvdimm tree with the powerpc tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the userns tree with the asm-generic tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the userns tree with the block tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the char-misc tree with the arm-soc tree
  • From: Greg KH <greg@xxxxxxxxx>
• Re: linux-next: manual merge of the char-misc tree with the net-next tree
  • From: Greg KH <greg@xxxxxxxxx>
• next/pending-fixes baseline: 198 runs, 4 regressions (v5.17-rc8-96-g702087d7e205)
  • From: "kernelci.org bot" <bot@xxxxxxxxxxxx>
• linux-next: manual merge of the char-misc tree with the arm-soc tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the char-misc tree with the net-next tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• mmotm 2022-03-14-22-42 uploaded
  • From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
• Re: linux-next: build failure after merge of the tip tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: build failure after merge of the tip tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the ftrace tree with the nfsd tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• next/pending-fixes build: 188 builds: 5 failed, 183 passed, 7 errors, 4 warnings (v5.17-rc8-96-g702087d7e205)
  • From: "kernelci.org bot" <bot@xxxxxxxxxxxx>
• linux-next: build failure after merge of the tip tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: build warnings after merge of the tip tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the tip tree with the net-next tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the tip tree with the powerpc tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: Signed-off-by missing for commit in the v4l-dvb-next tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: Fixes tag needs some work in the hid tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: [next] arm: Internal error: Oops: 5 PC is at __read_once_word_nocheck
  • From: Ard Biesheuvel <ardb@xxxxxxxxxx>
• Re: [next] arm: Internal error: Oops: 5 PC is at __read_once_word_nocheck
  • From: Naresh Kamboju <naresh.kamboju@xxxxxxxxxx>
• linux-next: Fixes tag needs some work in the ext4 tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: Signed-off-by missing for commit in the tip tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: [PATCH] user_events: Use alloc_pages instead of kzalloc for register pages
  • From: Beau Belgrave <beaub@xxxxxxxxxxxxxxxxxxx>
• Re: [next] arm64: allmodconfig: kernel BUG at include/linux/page-flags.h:509
  • From: Beau Belgrave <beaub@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH] user_events: Use alloc_pages instead of kzalloc for register pages
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [next] arm64: allmodconfig: kernel BUG at include/linux/page-flags.h:509
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [PATCH] user_events: Use alloc_pages instead of kzalloc for register pages
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [next] arm64: allmodconfig: kernel BUG at include/linux/page-flags.h:509
  • From: Beau Belgrave <beaub@xxxxxxxxxxxxxxxxxxx>
• Re: [next] arm64: allmodconfig: kernel BUG at include/linux/page-flags.h:509
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• next/master baseline: 391 runs, 39 regressions (next-20220310)
  • From: "kernelci.org bot" <bot@xxxxxxxxxxxx>
• [PATCH] user_events: Use alloc_pages instead of kzalloc for register pages
  • From: Beau Belgrave <beaub@xxxxxxxxxxxxxxxxxxx>
• Re: mmotm 2022-03-10-21-38 uploaded (drivers/media/platform/amphion/)
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
• Re: [next] arm64: allmodconfig: kernel BUG at include/linux/page-flags.h:509
  • From: Beau Belgrave <beaub@xxxxxxxxxxxxxxxxxxx>
• Re: [next] arm64: allmodconfig: kernel BUG at include/linux/page-flags.h:509
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• next/master build: 164 builds: 12 failed, 152 passed, 23 errors, 59 warnings (next-20220310)
  • From: "kernelci.org bot" <bot@xxxxxxxxxxxx>
• linux-next: Signed-off-by missing for commits in the ksmbd tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: Fixes tag needs some work in the uml tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: [next] arm64: allmodconfig: kernel BUG at include/linux/page-flags.h:509
  • From: Beau Belgrave <beaub@xxxxxxxxxxxxxxxxxxx>
• Re: [next] arm64: allmodconfig: kernel BUG at include/linux/page-flags.h:509
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• [next] arm64: allmodconfig: kernel BUG at include/linux/page-flags.h:509
  • From: Anders Roxell <anders.roxell@xxxxxxxxxx>
• linux-next: No tree today
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• next/pending-fixes baseline: 270 runs, 27 regressions (v5.17-rc7-273-g090ff5ac1521)
  • From: "kernelci.org bot" <bot@xxxxxxxxxxxx>
• mmotm 2022-03-10-21-38 uploaded
  • From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
• next/pending-fixes build: 167 builds: 6 failed, 161 passed, 8 errors, 6 warnings (v5.17-rc7-273-g090ff5ac1521)
  • From: "kernelci.org bot" <bot@xxxxxxxxxxxx>
• next/pending-fixes baseline: 284 runs, 28 regressions (v5.17-rc7-220-g483b57a0f972)
  • From: "kernelci.org bot" <bot@xxxxxxxxxxxx>
• next/pending-fixes build: 153 builds: 5 failed, 148 passed, 6 errors, 2 warnings (v5.17-rc7-220-g483b57a0f972)
  • From: "kernelci.org bot" <bot@xxxxxxxxxxxx>
• Re: [next] arm: Internal error: Oops: 5 PC is at __read_once_word_nocheck
  • From: "Russell King (Oracle)" <linux@xxxxxxxxxxxxxxx>
• Re: [next] arm: Internal error: Oops: 5 PC is at __read_once_word_nocheck
  • From: Ard Biesheuvel <ardb@xxxxxxxxxx>
• Re: [next] arm: Internal error: Oops: 5 PC is at __read_once_word_nocheck
  • From: Naresh Kamboju <naresh.kamboju@xxxxxxxxxx>
• Re: [next] arm: Internal error: Oops: 5 PC is at __read_once_word_nocheck
  • From: Ard Biesheuvel <ardb@xxxxxxxxxx>
• [no subject]
  • From: Unknown
• [no subject]
  • From: Unknown
• Re: [next] arm: Internal error: Oops: 5 PC is at __read_once_word_nocheck
  • From: Naresh Kamboju <naresh.kamboju@xxxxxxxxxx>
• Re: Upcoming merge conflict between s390 and kvm / kvms390 trees
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Upcoming merge conflict between s390 and kvm / kvms390 trees
  • From: Vasily Gorbik <gor@xxxxxxxxxxxxx>
• Re: mmotm 2022-03-09-23-28 uploaded (drivers/perf/marvell_cn10k_ddr_pmu.c)
  • From: Arnd Bergmann <arnd@xxxxxxxx>
• Re: linux-next: panic on 20220307 tree
  • From: David Hildenbrand <david@xxxxxxxxxx>
• Re: mmotm 2022-03-09-23-28 uploaded (drivers/perf/marvell_cn10k_ddr_pmu.c)
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
• Re: linux-next: panic on 20220307 tree
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• Re: [next] ld.lld: error: ./arch/arm/kernel/vmlinux.lds:34: AT expected, but got NOCROSSREFS
  • From: Nathan Chancellor <nathan@xxxxxxxxxx>
• Re: [next] arm: Internal error: Oops: 5 PC is at __read_once_word_nocheck
  • From: Ard Biesheuvel <ardb@xxxxxxxxxx>
• Re: [next] arm: Internal error: Oops: 5 PC is at __read_once_word_nocheck
  • From: "Russell King (Oracle)" <linux@xxxxxxxxxxxxxxx>
• Re: [next] arm: Internal error: Oops: 5 PC is at __read_once_word_nocheck
  • From: "Russell King (Oracle)" <linux@xxxxxxxxxxxxxxx>
• [next] ld.lld: error: ./arch/arm/kernel/vmlinux.lds:34: AT expected, but got NOCROSSREFS
  • From: Naresh Kamboju <naresh.kamboju@xxxxxxxxxx>
• Re: linux-next: build warning after merge of the memblock tree
  • From: Mike Rapoport <rppt@xxxxxxxxxx>
• linux-next: build warning after merge of the memblock tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: Signed-off-by missing for commits in the pci tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: Tree for Mar 10
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: build failure after merge of the akpm-current tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• mmotm 2022-03-09-23-28 uploaded
  • From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
• linux-next: manual merge of the net-next tree with the net tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: [next] arm: Internal error: Oops: 5 PC is at __read_once_word_nocheck
  • From: Ard Biesheuvel <ardb@xxxxxxxxxx>
• next/master baseline: 458 runs, 37 regressions (next-20220309)
  • From: "kernelci.org bot" <bot@xxxxxxxxxxxx>
• Re: [next] arm: Internal error: Oops: 5 PC is at __read_once_word_nocheck
  • From: "Russell King (Oracle)" <linux@xxxxxxxxxxxxxxx>
• Re: [next] arm: Internal error: Oops: 5 PC is at __read_once_word_nocheck
  • From: Ard Biesheuvel <ardb@xxxxxxxxxx>
• Re: next/master build: 224 builds: 30 failed, 194 passed, 97 errors, 370 warnings (next-20220309)
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• Re: [next] arm: Internal error: Oops: 5 PC is at __read_once_word_nocheck
  • From: "Russell King (Oracle)" <linux@xxxxxxxxxxxxxxx>
• Re: next/master build: 224 builds: 30 failed, 194 passed, 97 errors, 370 warnings (next-20220309)
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• Re: [next] arm: Internal error: Oops: 5 PC is at __read_once_word_nocheck
  • From: Ard Biesheuvel <ardb@xxxxxxxxxx>
• Re: linux-next: build failure after merge of the kspp tree
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• Re: linux-next: build failure after merge of the kspp tree
  • From: Hans de Goede <hdegoede@xxxxxxxxxx>
• Re: [next] arm: Internal error: Oops: 5 PC is at __read_once_word_nocheck
  • From: "Russell King (Oracle)" <linux@xxxxxxxxxxxxxxx>
• Re: [next] arm: Internal error: Oops: 5 PC is at __read_once_word_nocheck
  • From: Ard Biesheuvel <ardb@xxxxxxxxxx>
• Re: linux-next: build failure after merge of the kspp tree
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• next/master build: 224 builds: 30 failed, 194 passed, 97 errors, 370 warnings (next-20220309)
  • From: "kernelci.org bot" <bot@xxxxxxxxxxxx>
• Re: [next] arm: Internal error: Oops: 5 PC is at __read_once_word_nocheck
  • From: Naresh Kamboju <naresh.kamboju@xxxxxxxxxx>
• Re: [next] arm: Internal error: Oops: 5 PC is at __read_once_word_nocheck
  • From: Ard Biesheuvel <ardb@xxxxxxxxxx>
• Re: [next] arm: Internal error: Oops: 5 PC is at __read_once_word_nocheck
  • From: "Russell King (Oracle)" <linux@xxxxxxxxxxxxxxx>
• Re: [next] arm: Internal error: Oops: 5 PC is at __read_once_word_nocheck
  • From: Ard Biesheuvel <ardb@xxxxxxxxxx>
• Re: [next] arm: Internal error: Oops: 5 PC is at __read_once_word_nocheck
  • From: Naresh Kamboju <naresh.kamboju@xxxxxxxxxx>
• Re: [next] arm: Internal error: Oops: 5 PC is at __read_once_word_nocheck
  • From: Naresh Kamboju <naresh.kamboju@xxxxxxxxxx>
• Re: linux-next: manual merge of the arm64 tree with Linus' tree
  • From: Will Deacon <will@xxxxxxxxxx>
• Re: linux-next: build warning after merge of the arm64 tree
  • From: Will Deacon <will@xxxxxxxxxx>
• linux-next: Fixes tag needs some work in the qcom tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: Tree for Mar 9
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: build warning after merge of the arm64 tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• next/pending-fixes baseline: 279 runs, 26 regressions (v5.17-rc7-200-gfb8a41b34095)
  • From: "kernelci.org bot" <bot@xxxxxxxxxxxx>
• Re: [next] arm: Internal error: Oops: 5 PC is at __read_once_word_nocheck
  • From: Ard Biesheuvel <ardb@xxxxxxxxxx>
• Re: [next] arm: Internal error: Oops: 5 PC is at __read_once_word_nocheck
  • From: "Russell King (Oracle)" <linux@xxxxxxxxxxxxxxx>
• linux-next: build failure after merge of the kspp tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• [next] arm: Internal error: Oops: 5 PC is at __read_once_word_nocheck
  • From: Naresh Kamboju <naresh.kamboju@xxxxxxxxxx>
• Re: linux-next: manual merge of the mfd tree with the arm-soc tree
  • From: Krzysztof Kozlowski <krzysztof.kozlowski@xxxxxxxxxxxxx>
• next/pending-fixes build: 179 builds: 15 failed, 164 passed, 76 errors, 5 warnings (v5.17-rc7-200-gfb8a41b34095)
  • From: "kernelci.org bot" <bot@xxxxxxxxxxxx>
• Re: linux-next: build warning after merge of the vhost tree
  • From: Xuan Zhuo <xuanzhuo@xxxxxxxxxxxxxxxxx>
• Re: linux-next: build warning after merge of the vhost tree
  • From: Xuan Zhuo <xuanzhuo@xxxxxxxxxxxxxxxxx>
• Re: linux-next: build warning after merge of the vhost tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: build failure after merge of the block tree
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: linux-next: build failure after merge of the block tree
  • From: Jens Axboe <axboe@xxxxxxxxx>
• linux-next: manual merge of the mfd tree with the arm-soc tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: build failure after merge of the block tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the arm64 tree with Linus' tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the arm64 tree with Linus' tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the arm tree with Linus' tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: Fixes tag needs some work in the i3c tree
  • From: Alexandre Belloni <alexandre.belloni@xxxxxxxxxxx>
• linux-next: Fixes tag needs some work in the sound-asoc tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: Fixes tag needs some work in the i3c tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: Signed-off-by missing for commit in the arm-soc tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: Signed-off-by missing for commit in the arm64 tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: mmotm 2022-03-06-20-33 uploaded (x86-android-tablets)
  • From: Hans de Goede <hdegoede@xxxxxxxxxx>
• next/master baseline: 466 runs, 24 regressions (next-20220308)
  • From: "kernelci.org bot" <bot@xxxxxxxxxxxx>
• Re: linux-next: build failure after merge of the amdgpu tree
  • From: Noralf Trønnes <noralf@xxxxxxxxxxx>
• next/master build: 224 builds: 17 failed, 207 passed, 64 errors, 341 warnings (next-20220308)
  • From: "kernelci.org bot" <bot@xxxxxxxxxxxx>
• RE: [EXT] linux-next: build warnings after merge of the v4l-dvb-next tree
  • From: Ming Qian <ming.qian@xxxxxxx>