Linux Next

• Thread Index

• 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>
• linux-next: Tree for Mar 8
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: Signed-off-by missing for commit in the v4l-dvb-next tree
  • From: Hans Verkuil <hverkuil-cisco@xxxxxxxxx>
• linux-next: build warnings after merge of the v4l-dvb-next tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the vhost tree with the block tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• next/pending-fixes build: 198 builds: 6 failed, 192 passed, 7 errors, 6 warnings (v5.17-rc7-140-g856f0c2997ce)
  • From: "kernelci.org bot" <bot@xxxxxxxxxxxx>
• linux-next: panic on 20220307 tree
  • From: Murphy Zhou <jencce.kernel@xxxxxxxxx>
• linux-next: manual merge of the net-next tree with the staging.current tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: Signed-off-by missing for commits in the net-next tree
  • From: Jakub Kicinski <kuba@xxxxxxxxxx>
• Re: linux-next: Signed-off-by missing for commits in the net-next tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: mmotm 2022-03-06-20-33 uploaded (sound/soc/intel/boards/)
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
• Re: linux-next: Signed-off-by missing for commits in the net-next tree
  • From: Jakub Kicinski <kuba@xxxxxxxxxx>
• Re: mmotm 2022-03-06-20-33 uploaded (sound/soc/intel/boards/)
  • From: Pierre-Louis Bossart <pierre-louis.bossart@xxxxxxxxxxxxxxx>
• Re: linux-next: build failure after merge of the akpm tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: mmotm 2022-03-06-20-33 uploaded (sound/soc/codecs/snd-soc-lpass-[rt]x-macro.ko)
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
• next/master baseline: 95 runs, 10 regressions (next-20220307)
  • From: "kernelci.org bot" <bot@xxxxxxxxxxxx>
• Re: mmotm 2022-03-06-20-33 uploaded (x86-android-tablets)
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
• Re: mmotm 2022-03-06-20-33 uploaded (sound/soc/intel/boards/)
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
• linux-next: Signed-off-by missing for commit in the v4l-dvb-next tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: build failure after merge of the net-next tree
  • From: Maciej Fijalkowski <maciej.fijalkowski@xxxxxxxxx>
• Re: [next] mips-mt.c:233:19: error: conflicting types for 'mt_init'
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
• Re: [next] mips-mt.c:233:19: error: conflicting types for 'mt_init'
  • From: Liam Howlett <liam.howlett@xxxxxxxxxx>
• Re: [PATCH vfio-next] PCI/IOV: Fix wrong kernel-doc identifier
  • From: Alex Williamson <alex.williamson@xxxxxxxxxx>
• Re: [PATCH vfio-next] PCI/IOV: Fix wrong kernel-doc identifier
  • From: Bjorn Helgaas <helgaas@xxxxxxxxxx>
• next/master build: 177 builds: 62 failed, 115 passed, 330 errors, 329 warnings (next-20220307)
  • From: "kernelci.org bot" <bot@xxxxxxxxxxxx>
• Re: linux-next: build failure after merge of the net-next tree
  • From: Dimitris Michailidis <d.michailidis@xxxxxxxxxxxx>
• Re: [next] mips: madvise.c:55:7: error: 'MADV_DONTNEED_LOCKED' undeclared
  • From: Johannes Weiner <hannes@xxxxxxxxxxx>
• Re: linux-next: build failure after merge of the akpm tree
  • From: Johannes Weiner <hannes@xxxxxxxxxxx>
• [PATCH] mm: madvise: MADV_DONTNEED_LOCKED fix
  • From: Johannes Weiner <hannes@xxxxxxxxxxx>
• Re: [PATCH vfio-next] PCI/IOV: Fix wrong kernel-doc identifier
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
• [next] mips: madvise.c:55:7: error: 'MADV_DONTNEED_LOCKED' undeclared
  • From: Naresh Kamboju <naresh.kamboju@xxxxxxxxxx>
• Re: [PATCH vfio-next] PCI/IOV: Fix wrong kernel-doc identifier
  • From: Alex Williamson <alex.williamson@xxxxxxxxxx>
• Re: linux-next: build failure after merge of the amdgpu tree
  • From: Mark Brown <broonie@xxxxxxxxxx>
• [PATCH vfio-next] PCI/IOV: Fix wrong kernel-doc identifier
  • From: Leon Romanovsky <leon@xxxxxxxxxx>
• Re: linux-next: build warning after merge of the vhost tree
  • From: "Michael S. Tsirkin" <mst@xxxxxxxxxx>
• linux-next: build failure after merge of the akpm tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: build failure after merge of the net-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: build warning after merge of the vhost tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: build warning after merge of the vhost tree
  • From: Xuan Zhuo <xuanzhuo@xxxxxxxxxxxxxxxxx>
• Re: linux-next: Signed-off-by missing for commit in the fscache tree
  • From: David Howells <dhowells@xxxxxxxxxx>
• Re: linux-next: build warning after merge of the vhost tree
  • From: "Michael S. Tsirkin" <mst@xxxxxxxxxx>
• linux-next: Tree for Mar 7
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: build failure after merge of the amdgpu tree
  • From: Uwe Kleine-König <u.kleine-koenig@xxxxxxxxxxxxxx>
• Re: linux-next: build warning after merge of the vhost tree
  • From: Xuan Zhuo <xuanzhuo@xxxxxxxxxxxxxxxxx>
• Re: [External] Re: [next] WARNING: suspicious RCU usage : include/linux/cgroup.h:494 suspicious rcu_dereference_check() usage
  • From: Naresh Kamboju <naresh.kamboju@xxxxxxxxxx>
• next/pending-fixes baseline: 408 runs, 8 regressions (v5.17-rc6-376-g477ac50bab9c)
  • From: "kernelci.org bot" <bot@xxxxxxxxxxxx>
• linux-next: build warning after merge of the vhost tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the vhost tree with the block tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• mmotm 2022-03-06-20-33 uploaded
  • From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
• linux-next: manual merge of the scsi tree with the block tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the scsi tree with the block tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the tip tree with the iommu tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• next/pending-fixes build: 168 builds: 5 failed, 163 passed, 4 errors, 4 warnings (v5.17-rc6-376-g477ac50bab9c)
  • From: "kernelci.org bot" <bot@xxxxxxxxxxxx>
• linux-next: build failure after merge of the amdgpu 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: Signed-off-by missing for commit in the iommu tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: Fixes tag needs some work in the amdgpu tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: Signed-off-by missing for commits in the net-next tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: Signed-off-by missing for commit in the fscache tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: build warnings after merge of the vfio tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: Signed-off-by missing for commit in the at91 tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: [next] mips-mt.c:233:19: error: conflicting types for 'mt_init'
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
• next/master baseline: 340 runs, 18 regressions (next-20220304)
  • From: "kernelci.org bot" <bot@xxxxxxxxxxxx>
• Re: [External] Re: [next] WARNING: suspicious RCU usage : include/linux/cgroup.h:494 suspicious rcu_dereference_check() usage
  • From: Zhouyi Zhou <zhouzhouyi@xxxxxxxxx>
• Re: [External] Re: [next] WARNING: suspicious RCU usage : include/linux/cgroup.h:494 suspicious rcu_dereference_check() usage
  • From: Chengming Zhou <zhouchengming@xxxxxxxxxxxxx>
• next/master build: 181 builds: 11 failed, 170 passed, 29 errors, 273 warnings (next-20220304)
  • From: "kernelci.org bot" <bot@xxxxxxxxxxxx>
• Re: [next] WARNING: suspicious RCU usage : include/linux/cgroup.h:494 suspicious rcu_dereference_check() usage
  • From: "Paul E. McKenney" <paulmck@xxxxxxxxxx>
• Re: [next] WARNING: suspicious RCU usage : include/linux/cgroup.h:494 suspicious rcu_dereference_check() usage
  • From: Zhouyi Zhou <zhouzhouyi@xxxxxxxxx>
• Re: [next] WARNING: suspicious RCU usage : include/linux/cgroup.h:494 suspicious rcu_dereference_check() usage
  • From: "Paul E. McKenney" <paulmck@xxxxxxxxxx>
• Re: [next] WARNING: suspicious RCU usage : include/linux/cgroup.h:494 suspicious rcu_dereference_check() usage
  • From: Zhouyi Zhou <zhouzhouyi@xxxxxxxxx>
• Re: mmotm 2022-03-03-21-24 uploaded (security/apparmor/policy_unpack.o)
  • From: John Johansen <john.johansen@xxxxxxxxxxxxx>
• Re: mmotm 2022-03-03-21-24 uploaded (security/apparmor/policy_unpack.o)
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
• Re: mmotm 2022-03-03-21-24 uploaded (sound/soc/intel/boards/)
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
• Re: mmotm 2022-03-03-21-24 uploaded [drivers/platform/x86/x86-android-tablets.ko]
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
• [next] WARNING: suspicious RCU usage : include/linux/cgroup.h:494 suspicious rcu_dereference_check() usage
  • From: Naresh Kamboju <naresh.kamboju@xxxxxxxxxx>
• next/pending-fixes baseline: 168 runs, 3 regressions (v5.17-rc6-312-gf15bf60c638f)
  • From: "kernelci.org bot" <bot@xxxxxxxxxxxx>
• [syzbot] linux-next boot error: WARNING: suspicious RCU usage in cpuacct_charge
  • From: syzbot <syzbot+16e3f2c77e7c5a0113f9@xxxxxxxxxxxxxxxxxxxxxxxxx>
• linux-next: Tree for Mar 4
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• next/pending-fixes build: 139 builds: 4 failed, 135 passed, 7 errors, 6 warnings (v5.17-rc6-312-gf15bf60c638f)
  • From: "kernelci.org bot" <bot@xxxxxxxxxxxx>
• Re: mmotm 2022-03-02-16-53 uploaded (drivers/i2c/busses/i2c-designware-platdrv.c)
  • From: Wolfram Sang <wsa@xxxxxxxxxx>
• mmotm 2022-03-03-21-24 uploaded
  • From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
• Re: mmotm 2022-02-23-21-20 uploaded (Kconfig warning: SND_SOC_WCD938X)
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
• Re: mmotm 2022-03-02-16-53 uploaded (drivers/i2c/busses/i2c-designware-platdrv.c)
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
• next/pending-fixes baseline: 244 runs, 4 regressions (v5.17-rc6-278-g34490bca674f)
  • From: "kernelci.org bot" <bot@xxxxxxxxxxxx>
• next/pending-fixes build: 153 builds: 4 failed, 149 passed, 5 errors, 1 warning (v5.17-rc6-278-g34490bca674f)
  • From: "kernelci.org bot" <bot@xxxxxxxxxxxx>
• next/master baseline: 524 runs, 16 regressions (next-20220303)
  • From: "kernelci.org bot" <bot@xxxxxxxxxxxx>
• Re: linux-next: build failure after merge of the arm-soc tree
  • From: Arnd Bergmann <arnd@xxxxxxxx>
• Re: linux-next: build failure after merge of the soundwire tree
  • From: Vinod Koul <vkoul@xxxxxxxxxx>
• next/master build: 217 builds: 11 failed, 206 passed, 23 errors, 341 warnings (next-20220303)
  • From: "kernelci.org bot" <bot@xxxxxxxxxxxx>
• Re: [next-20220225] powerpc boot broken with maple tree code ?
  • From: Abdul Haleem <abdhalee@xxxxxxxxxxxxxxxxxx>
• Re: linux-next: build failure after merge of the soundwire tree
  • From: Srinivas Kandagatla <srinivas.kandagatla@xxxxxxxxxx>
• linux-next: build failure after merge of the soundwire tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: build failure after merge of the random tree
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• linux-next: Signed-off-by missing for commit in the tip tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: build warning after merge of the net-next tree
  • From: "dust.li" <dust.li@xxxxxxxxxxxxxxxxx>
• linux-next: Fixes tag needs some work in the net tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: build warning after merge of the fscache tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: Tree for Mar 3
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: build warning after merge of the net-next tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: build warning after merge of the net-next tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the akpm-current tree with the asm-generic tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the akpm-current tree with the kspp tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: build failure after merge of the random tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: build failure after merge of the kspp tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the folio tree with the asm-generic tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• lkft kselftest for next-20220302
  • From: lkft@xxxxxxxxxx
• linux-next: manual merge of the drivers-x86 tree with the pm tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• mmotm 2022-03-02-16-53 uploaded
  • From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
• Re: [next] Internal error: aarch64 BRK: f20003e8 at pc : has_cpuid_feature
  • From: Suzuki K Poulose <suzuki.poulose@xxxxxxx>
• Re: linux-next: Fixes tag needs some work in the amdgpu tree
  • From: Alex Deucher <alexdeucher@xxxxxxxxx>
• Re: [next] arm64: db410c: Internal error: Oops: 96000004 - msm_gpu_pm_suspend
  • From: Rob Clark <robdclark@xxxxxxxxxxxx>
• Re: linux-next: Fixes tag needs some work in the amdgpu tree
  • From: Luben Tuikov <luben.tuikov@xxxxxxx>
• [next] Internal error: aarch64 BRK: f20003e8 at pc : has_cpuid_feature
  • From: Naresh Kamboju <naresh.kamboju@xxxxxxxxxx>
• 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 amdgpu tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• [next] arm64: db410c: Internal error: Oops: 96000004 - msm_gpu_pm_suspend
  • From: Naresh Kamboju <naresh.kamboju@xxxxxxxxxx>
• Re: [next] warning: the frame size of 1120 bytes is larger than 1024 bytes [-Wframe-larger-than=]
  • From: Matthew Wilcox <willy@xxxxxxxxxxxxx>
• Re: linux-next: build warning after merge of the drm tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: MSM8960: gpu/drm/dp/drm_dp.c:59:27: warning: array subscript 10 is outside, array bounds of 'const u8[6]'
  • From: Jani Nikula <jani.nikula@xxxxxxxxx>
• linux-next: removal of the nds32 tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxx>
• linux-next: Signed-off-by missing for commit in the arm-soc tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: Fixes tag needs some work in the drivers-x86 tree
  • From: Hans de Goede <hdegoede@xxxxxxxxxx>
• linux-next: Tree for Mar 2
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: build warning after merge of the drm tree
  • From: Hans de Goede <hdegoede@xxxxxxxxxx>
• Re: linux-next: manual merge of the char-misc tree with the mfd tree
  • From: Robert Marko <robert.marko@xxxxxxxxxx>
• Re: linux-next: build failure after merge of the arm-soc tree
  • From: Matthias Brugger <matthias.bgg@xxxxxxxxx>
• Re: linux-next: build failure after merge of the kspp tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the char-misc tree with the mfd tree
  • From: Lee Jones <lee.jones@xxxxxxxxxx>
• Re: linux-next: manual merge of the char-misc tree with the mfd tree
  • From: Lee Jones <lee.jones@xxxxxxxxxx>
• Re: [next-20220225][Oops][ppc] lvm snapshot merge results kernel panics (throtl_pending_timer_fn)
  • From: Ming Lei <ming.lei@xxxxxxxxxx>
• [next-20220225][Oops][ppc] lvm snapshot merge results kernel panics (throtl_pending_timer_fn)
  • From: Abdul Haleem <abdhalee@xxxxxxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the char-misc tree with the mfd tree
  • From: Lee Jones <lee.jones@xxxxxxxxxx>
• Re: linux-next: build failure after merge of the arm-soc tree
  • From: Arnd Bergmann <arnd@xxxxxxxx>
• lkft kselftest for next-20220301
  • From: lkft@xxxxxxxxxx
• Re: linux-next: build failure after merge of the mhi tree
  • From: Manivannan Sadhasivam <manivannan.sadhasivam@xxxxxxxxxx>
• [next] warning: the frame size of 1120 bytes is larger than 1024 bytes [-Wframe-larger-than=]
  • From: Naresh Kamboju <naresh.kamboju@xxxxxxxxxx>
• linux-next: build failure after merge of the mhi tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• [next-20220225] powerpc boot broken with maple tree code ?
  • From: Abdul Haleem <abdhalee@xxxxxxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the net-next tree with the net tree
  • From: Tony Lu <tonylu@xxxxxxxxxxxxxxxxx>
• Re: linux-next: build warning after merge of the drm-misc tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxx>
• Re: linux-next: build warning after merge of the drm-misc tree
  • From: Andrey Grodzovsky <andrey.grodzovsky@xxxxxxx>
• MSM8960: gpu/drm/dp/drm_dp.c:59:27: warning: array subscript 10 is outside, array bounds of 'const u8[6]'
  • From: Rudraksha Gupta <guptarud@xxxxxxxxx>
• Re: linux-next: Fixes tag needs some work in the drm-msm tree
  • From: Dmitry Baryshkov <dmitry.baryshkov@xxxxxxxxxx>
• Re: linux-next: build warning after merge of the drm tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: build warning after merge of the drm tree
  • 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 after merge of the net-next tree
  • From: Jakub Kicinski <kuba@xxxxxxxxxx>
• linux-next: build failure after merge of the net-next tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: Fixes tag needs some work in the drm-msm tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the net-next tree with the net tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the char-misc tree with the mfd tree
  • From: Robert Marko <robert.marko@xxxxxxxxxx>
• linux-next: build failure after merge of the arm-soc tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: Signed-off-by missing for commits in the pci tree
  • From: Bjorn Helgaas <helgaas@xxxxxxxxxx>
• Re: linux-next: build failure after merge of the char-misc tree
  • From: Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the char-misc tree with the mfd tree
  • From: Greg KH <greg@xxxxxxxxx>
• linux-next: Fixes tag needs some work in the drivers-x86 tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: Signed-off-by missing for commit in the arm-soc tree
  • From: Arnd Bergmann <arnd@xxxxxxxx>
• linux-next: Signed-off-by missing for commits in the pci tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: 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 arm-soc tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• next/pending-fixes baseline: 224 runs, 4 regressions (v5.17-rc6-208-gaea6d79fce16)
  • From: "kernelci.org bot" <bot@xxxxxxxxxxxx>
• next/master baseline: 416 runs, 4 regressions (next-20220301)
  • From: "kernelci.org bot" <bot@xxxxxxxxxxxx>
• Re: linux-next: build warnings after merge of the pci tree
  • From: Bjorn Helgaas <helgaas@xxxxxxxxxx>
• Re: linux-next: build warnings after merge of the drivers-x86 tree
  • From: Hans de Goede <hdegoede@xxxxxxxxxx>
• next/pending-fixes build: 192 builds: 4 failed, 188 passed, 4 errors, 6 warnings (v5.17-rc6-208-gaea6d79fce16)
  • From: "kernelci.org bot" <bot@xxxxxxxxxxxx>
• next/master build: 205 builds: 41 failed, 164 passed, 52 errors, 305 warnings (next-20220301)
  • From: "kernelci.org bot" <bot@xxxxxxxxxxxx>
• Re: linux-next: manual merge of the char-misc tree with the mfd tree
  • From: Lee Jones <lee.jones@xxxxxxxxxx>
• Re: linux-next: manual merge of the char-misc tree with the mfd tree
  • From: Greg KH <greg@xxxxxxxxx>
• linux-next: Tree for Mar 1
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the char-misc tree with the mfd tree
  • From: Lee Jones <lee.jones@xxxxxxxxxx>
• linux-next: build warnings after merge of the drivers-x86 tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: build warning after merge of the net-next tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the scsi-mkp tree with the block tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the scsi-mkp tree with the block tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• next/master baseline: 501 runs, 7 regressions (next-20220228)
  • From: "kernelci.org bot" <bot@xxxxxxxxxxxx>
• Re: linux-next: build failure after merge of the char-misc tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the spi tree with the arm-soc tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: build warnings after merge of the pci tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• next/master build: 206 builds: 14 failed, 192 passed, 28 errors, 310 warnings (next-20220228)
  • From: "kernelci.org bot" <bot@xxxxxxxxxxxx>
• linux-next: manual merge of the drm tree with the v4l-dvb tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: mmotm 2022-02-28-14-45 uploaded (drivers/tty/serial/sunplus-uart.c:)
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
• Re: mmotm 2022-02-28-14-45 uploaded (drivers/tty/serial/sunplus-uart.c:)
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
• Re: linux-next: Fixes tag needs some work in the modules tree
  • From: Luis Chamberlain <mcgrof@xxxxxxxxxx>
• linux-next: Fixes tag needs some work in the modules tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: change to Next/SHA1s ?
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• Re: linux-next: build failure after merge of the kspp tree
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• Re: change to Next/SHA1s ?
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• mmotm 2022-02-28-14-45 uploaded
  • From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
• linux-next: build failure after merge of the kspp tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the char-misc tree with the mfd tree
  • From: Greg KH <greg@xxxxxxxxx>
• change to Next/SHA1s ?
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• Re: linux-next: build failure after merge of the akpm-current tree
  • From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
• Re: linux-next: build failure after merge of the modules tree
  • From: Luis Chamberlain <mcgrof@xxxxxxxxxx>
• Re: linux-next: Fixes tag needs some work in the arm-soc tree
  • From: Arnd Bergmann <arnd@xxxxxxxx>
• linux-next: Fixes tag needs some work in the arm-soc tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: Tree for Feb 28
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: build failure after merge of the drm tree
  • From: Robert Foss <robert.foss@xxxxxxxxxx>
• linux-next: build failure after merge of the akpm-current tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: build failure after merge of the folio tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the char-misc tree with the mfd tree
  • From: Lee Jones <lee.jones@xxxxxxxxxx>
• Re: linux-next: Signed-off-by missing for commits in the arm-soc tree
  • From: Arnd Bergmann <arnd@xxxxxxxx>
• Re: [syzbot] linux-next test error: WARNING in __mod_memcg_lruvec_state
  • From: Sebastian Andrzej Siewior <bigeasy@xxxxxxxxxxxxx>
• Re: [syzbot] linux-next test error: WARNING in __mod_memcg_lruvec_state
  • From: syzbot <syzbot+a526c269335f529d25c8@xxxxxxxxxxxxxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the char-misc tree with the spi and tty trees
  • From: Greg KH <greg@xxxxxxxxx>
• Re: linux-next: manual merge of the tty tree with the spi tree
  • From: Greg KH <greg@xxxxxxxxx>
• Re: linux-next: manual merge of the char-misc tree with the mfd tree
  • From: Greg KH <greg@xxxxxxxxx>
• Re: linux-next: manual merge of the char-misc tree with the mfd tree
  • From: Lee Jones <lee.jones@xxxxxxxxxx>
• linux-next: manual merge of the char-misc tree with the mfd tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the char-misc tree with the spi and tty trees
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: build failure after merge of the mfd tree
  • From: Lee Jones <lee.jones@xxxxxxxxxx>
• linux-next: manual merge of the tty tree with the spi tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the pinctrl tree with the irqchip tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: build failure after merge of the drm tree
  • From: Dave Airlie <airlied@xxxxxxxxx>
• Re: linux-next: build failure after merge of the drm tree
  • From: Hsin-Yi Wang <hsinyi@xxxxxxxxxxxx>
• Re: [syzbot] linux-next test error: WARNING in __mod_memcg_lruvec_state
  • From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
• Re: linux-next: build failure after merge of the mfd tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• next/pending-fixes baseline: 335 runs, 3 regressions (v5.17-rc6-176-gb4e03e0dde48)
  • From: "kernelci.org bot" <bot@xxxxxxxxxxxx>
• Re: linux-next: build failure after merge of the modules tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: build failure after merge of the drm tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the drm-tegra tree with the drm tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the drm tree with Linus' tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• next/pending-fixes build: 187 builds: 6 failed, 181 passed, 8 errors, 6 warnings (v5.17-rc6-176-gb4e03e0dde48)
  • From: "kernelci.org bot" <bot@xxxxxxxxxxxx>
• linux-next: manual merge of the parisc-hd tree with the asm-generic tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the h8300 tree with the asm-generic tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the arm-soc tree with the arm tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: Tree for Feb 17
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: Please add for-next/execve
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: Signed-off-by missing for commits in the arm-soc tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: Fixes tag needs some work in the net tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: build failure after merge of the char-misc tree
  • From: Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx>
• lkft kselftest for next-20220225
  • From: lkft@xxxxxxxxxx
• [syzbot] linux-next test error: WARNING in __mod_memcg_lruvec_state
  • From: syzbot <syzbot+a526c269335f529d25c8@xxxxxxxxxxxxxxxxxxxxxxxxx>
• next/pending-fixes baseline: 325 runs, 4 regressions (v5.17-rc5-388-geb90b11d71c0)
  • From: "kernelci.org bot" <bot@xxxxxxxxxxxx>
• linux-next: Tree for Feb 25
  • From: broonie@xxxxxxxxxx
• Re: mmotm 2022-02-23-21-20 uploaded
  • From: Mark Brown <broonie@xxxxxxxxxx>
• next/pending-fixes build: 190 builds: 6 failed, 184 passed, 7 errors, 6 warnings (v5.17-rc5-388-geb90b11d71c0)
  • From: "kernelci.org bot" <bot@xxxxxxxxxxxx>
• linux-next: manual merge of the extcon tree with the battery tree
  • From: broonie@xxxxxxxxxx
• linux-next: build failure after merge of the char-misc tree
  • From: broonie@xxxxxxxxxx
• linux-next: manual merge of the drm-intel tree with the drm-intel-fixes tree
  • From: broonie@xxxxxxxxxx
• linux-next: build failure after merge of the drm tree
  • From: broonie@xxxxxxxxxx
• linux-next: manual merge of the drm tree with the drm-fixes tree
  • From: broonie@xxxxxxxxxx
• linux-next: manual merge of the drm tree with the drm-intel-fixes tree
  • From: broonie@xxxxxxxxxx
• Re: [PATCH] arm64: Change elfcore for_each_mte_vma() to use VMA iterator
  • From: Will Deacon <will@xxxxxxxxxx>
• build failure after merge of the at91 tree
  • From: broonie@xxxxxxxxxx
• Re: [next] next-20220223 kernel crash
  • From: Steffen Maier <maier@xxxxxxxxxxxxx>
• Re: linux-next: manual merge of the btrfs tree with the btrfs-fixes tree
  • From: David Sterba <dsterba@xxxxxxx>
• next/master baseline: 302 runs, 63 regressions (next-20220224)
  • From: "kernelci.org bot" <bot@xxxxxxxxxxxx>
• lkft kselftest for next-20220223
  • From: lkft@xxxxxxxxxx
• [next] mips-mt.c:233:19: error: conflicting types for 'mt_init'
  • From: Naresh Kamboju <naresh.kamboju@xxxxxxxxxx>
• mmotm 2022-02-24-22-38 uploaded
  • From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
• Re: mmotm 2022-02-23-21-20 uploaded
  • From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
• next/master build: 224 builds: 29 failed, 195 passed, 42 errors, 329 warnings (next-20220224)
  • From: "kernelci.org bot" <bot@xxxxxxxxxxxx>
• Re: linux-next: Tree for Feb 24 (kernel/sched/core,rt)
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
• Re: Please add for-next/execve
  • From: Mark Brown <broonie@xxxxxxxxxx>
• linux-next: Tree for Feb 24
  • From: broonie@xxxxxxxxxx
• Re: mmotm 2022-02-23-21-20 uploaded
  • From: Mark Brown <broonie@xxxxxxxxxx>
• lkft kselftest for next-20220222
  • From: lkft@xxxxxxxxxx
• Re: Please add for-next/execve
  • From: Matthew Wilcox <willy@xxxxxxxxxxxxx>
• lkft kselftest for next-20220217
  • From: lkft@xxxxxxxxxx
• next/pending-fixes baseline: 232 runs, 2 regressions (v5.17-rc5-317-g24650335a6e9)
  • From: "kernelci.org bot" <bot@xxxxxxxxxxxx>
• Re: mmotm 2022-02-23-21-20 uploaded [drivers/scsi/hisi_sas/hisi_sas_main.ko]
  • From: John Garry <john.garry@xxxxxxxxxx>
• Re: mmotm 2022-02-23-21-20 uploaded [drivers/net/wireless/intel/iwlwifi/iwlwifi.ko][2]
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
• Re: mmotm 2022-02-23-21-20 uploaded [drivers/scsi/hisi_sas/hisi_sas_main.ko]
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
• Re: mmotm 2022-02-23-21-20 uploaded (kernel/sched/rt.c)
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
• linux-next: manual merge of the drm-intel tree with the drm-intel-gt tree
  • From: broonie@xxxxxxxxxx
• Re: mmotm 2022-02-23-21-20 uploaded (iwlwifi + rfkill)
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
• Re: mmotm 2022-02-23-21-20 uploaded (Kconfig warning: SND_SOC_WCD938X)
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
• Re: [next] riscv/kernel/vdso.c:123:27: error: 'next' undeclared
  • From: Liam Howlett <liam.howlett@xxxxxxxxxx>
• Re: linux-next: Tree for Feb 22 (NFSD_V2_ACL)
  • From: Chuck Lever III <chuck.lever@xxxxxxxxxx>
• Re: linux-next: Tree for Feb 22 (NFSD_V2_ACL)
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
• Re: [next] mm/mmap.c:1962:25: error: passing argument 1 of 'vma_find' from incompatible pointer type
  • From: Liam Howlett <liam.howlett@xxxxxxxxxx>
• linux-next: manual merge of the drm tree with the drm-fixes tree
  • From: broonie@xxxxxxxxxx
• linux-next: manual merge of the net-next tree with the net tree
  • From: broonie@xxxxxxxxxx
• next/pending-fixes build: 193 builds: 6 failed, 187 passed, 7 errors, 6 warnings (v5.17-rc5-317-g24650335a6e9)
  • From: "kernelci.org bot" <bot@xxxxxxxxxxxx>
• Re: linux-next: Tree for Feb 22 (NFSD_V2_ACL)
  • From: Chuck Lever III <chuck.lever@xxxxxxxxxx>
• gpu/drm/dp/drm_dp.c:59:27: warning: array subscript 10 is outside array bounds of 'const u8[6]'
  • From: Naresh Kamboju <naresh.kamboju@xxxxxxxxxx>
• [next] riscv/kernel/vdso.c:123:27: error: 'next' undeclared
  • From: Naresh Kamboju <naresh.kamboju@xxxxxxxxxx>
• Re: linux-next: Tree for Feb 23 (drivers/net/ipa/ipa_power.o)
  • From: Alex Elder <elder@xxxxxxxx>
• [next] mm/mmap.c:1962:25: error: passing argument 1 of 'vma_find' from incompatible pointer type
  • From: Naresh Kamboju <naresh.kamboju@xxxxxxxxxx>
• linux-next: manual merge of the btrfs tree with the btrfs-fixes tree
  • From: broonie@xxxxxxxxxx
• [next] next-20220223 kernel crash
  • From: Naresh Kamboju <naresh.kamboju@xxxxxxxxxx>
• next/pending-fixes baseline: 216 runs, 2 regressions (v5.17-rc5-244-gd77a1b37f796)
  • From: "kernelci.org bot" <bot@xxxxxxxxxxxx>
• next/pending-fixes build: 194 builds: 6 failed, 188 passed, 7 errors, 4 warnings (v5.17-rc5-244-gd77a1b37f796)
  • From: "kernelci.org bot" <bot@xxxxxxxxxxxx>
• next/master baseline: 428 runs, 81 regressions (next-20220223)
  • From: "kernelci.org bot" <bot@xxxxxxxxxxxx>
• Re: linux-next: Tree for Feb 22 (NFSD_V2_ACL)
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
• Re: linux-next: Tree for Feb 23 (drivers/net/ipa/ipa_power.o)
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
• Please add for-next/execve
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• Re: mmotm 2022-02-23-21-20 uploaded
  • From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
• mmotm 2022-02-23-21-20 uploaded
  • From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
• next/master build: 214 builds: 31 failed, 183 passed, 43 errors, 341 warnings (next-20220223)
  • From: "kernelci.org bot" <bot@xxxxxxxxxxxx>
• Re: linux-next: manual merge of the folio tree with the maple tree
  • From: Mark Brown <broonie@xxxxxxxxxx>
• Re: [PATCH] arm64: Change elfcore for_each_mte_vma() to use VMA iterator
  • From: Liam Howlett <liam.howlett@xxxxxxxxxx>
• linux-next: Tree for Feb 23
  • From: broonie@xxxxxxxxxx
• linux-next: manual merge of the folio tree with the maple tree
  • From: broonie@xxxxxxxxxx
• linux-next: manual merge of the folio tree with the maple tree
  • From: broonie@xxxxxxxxxx
• linux-next: manual merge of the folio tree with the maple tree
  • From: broonie@xxxxxxxxxx
• linux-next: manual merge of the nvmem tree with the char-misc tree
  • From: broonie@xxxxxxxxxx
• linux-next: manual merge of the nvmem tree with the spi tree
  • From: broonie@xxxxxxxxxx
• linux-next: manual merge of the kvm tree with the kvm-fixes tree
  • From: broonie@xxxxxxxxxx
• Re: linux-next: build failure after merge of the mfd tree
  • From: Lee Jones <lee.jones@xxxxxxxxxx>
• linux-next: build failure after merge of the mfd tree
  • From: broonie@xxxxxxxxxx
• linux-next: manual merge of the drm-tegra tree with the drm tree
  • From: broonie@xxxxxxxxxx
• Re: linux-next: Tree for Feb 22 (NFSD_V2_ACL)
  • From: Chuck Lever III <chuck.lever@xxxxxxxxxx>
• linux-next: manual merge of the drm-intel tree with the drm-intel-fixes tree
  • From: broonie@xxxxxxxxxx
• Re: [PATCH] arm64: Change elfcore for_each_mte_vma() to use VMA iterator
  • From: Liam Howlett <liam.howlett@xxxxxxxxxx>
• Re: [PATCH] arm64: Change elfcore for_each_mte_vma() to use VMA iterator
  • From: Liam Howlett <liam.howlett@xxxxxxxxxx>
• Re: [PATCH] arm64: Change elfcore for_each_mte_vma() to use VMA iterator
  • From: kernel test robot <lkp@xxxxxxxxx>
• [REGRESSION] lkft kselftest for next-20220216
  • From: lkft@xxxxxxxxxx