[PATCH AUTOSEL 5.4 4/5] um: let 'make clean' properly clean underlying SUBARCH as well

2025-05-19 Thread Sasha Levin
From: Masahiro Yamada [ Upstream commit ab09da75700e9d25c7dfbc7f7934920beb5e39b9 ] Building the kernel with O= is affected by stale in-tree build artifacts. So, if the source tree is not clean, Kbuild displays the following: $ make ARCH=um O=build defconfig make[1]: Entering directory '/..

[PATCH AUTOSEL 5.10 4/6] um: let 'make clean' properly clean underlying SUBARCH as well

2025-05-19 Thread Sasha Levin
From: Masahiro Yamada [ Upstream commit ab09da75700e9d25c7dfbc7f7934920beb5e39b9 ] Building the kernel with O= is affected by stale in-tree build artifacts. So, if the source tree is not clean, Kbuild displays the following: $ make ARCH=um O=build defconfig make[1]: Entering directory '/..

[PATCH AUTOSEL 5.15 4/7] um: let 'make clean' properly clean underlying SUBARCH as well

2025-05-19 Thread Sasha Levin
From: Masahiro Yamada [ Upstream commit ab09da75700e9d25c7dfbc7f7934920beb5e39b9 ] Building the kernel with O= is affected by stale in-tree build artifacts. So, if the source tree is not clean, Kbuild displays the following: $ make ARCH=um O=build defconfig make[1]: Entering directory '/..

[PATCH AUTOSEL 6.1 4/8] um: let 'make clean' properly clean underlying SUBARCH as well

2025-05-19 Thread Sasha Levin
From: Masahiro Yamada [ Upstream commit ab09da75700e9d25c7dfbc7f7934920beb5e39b9 ] Building the kernel with O= is affected by stale in-tree build artifacts. So, if the source tree is not clean, Kbuild displays the following: $ make ARCH=um O=build defconfig make[1]: Entering directory '/..

[PATCH AUTOSEL 6.6 05/11] um: let 'make clean' properly clean underlying SUBARCH as well

2025-05-19 Thread Sasha Levin
From: Masahiro Yamada [ Upstream commit ab09da75700e9d25c7dfbc7f7934920beb5e39b9 ] Building the kernel with O= is affected by stale in-tree build artifacts. So, if the source tree is not clean, Kbuild displays the following: $ make ARCH=um O=build defconfig make[1]: Entering directory '/..

[PATCH AUTOSEL 6.12 05/18] um: let 'make clean' properly clean underlying SUBARCH as well

2025-05-19 Thread Sasha Levin
From: Masahiro Yamada [ Upstream commit ab09da75700e9d25c7dfbc7f7934920beb5e39b9 ] Building the kernel with O= is affected by stale in-tree build artifacts. So, if the source tree is not clean, Kbuild displays the following: $ make ARCH=um O=build defconfig make[1]: Entering directory '/..

[PATCH AUTOSEL 6.14 07/23] um: let 'make clean' properly clean underlying SUBARCH as well

2025-05-19 Thread Sasha Levin
From: Masahiro Yamada [ Upstream commit ab09da75700e9d25c7dfbc7f7934920beb5e39b9 ] Building the kernel with O= is affected by stale in-tree build artifacts. So, if the source tree is not clean, Kbuild displays the following: $ make ARCH=um O=build defconfig make[1]: Entering directory '/..

Re: [PATCH v2 10/13] arch, mm: set high_memory in free_area_init()

2025-05-19 Thread Mike Rapoport
Hi Alexandre, On Mon, May 19, 2025 at 05:54:23PM +0200, Alexandre Ghiti wrote: > Hi Mike, > > I encountered the same error as Pratyush and the above diff fixes it: do you > plan on sending this fix for 6.15? > > If so, you can add: > > Tested-by: Alexandre Ghiti Thanks! Here's the patch: http

Re: [PATCH v2 10/13] arch, mm: set high_memory in free_area_init()

2025-05-19 Thread Alexandre Ghiti
Hi Mike, On 5/16/25 19:01, Mike Rapoport wrote: Hi Pratyush, On Fri, May 16, 2025 at 05:28:17PM +0200, Pratyush Yadav wrote: Hi Mike, Andrew, On Thu, Mar 13 2025, Mike Rapoport wrote: From: "Mike Rapoport (Microsoft)" high_memory defines upper bound on the directly mapped memory. This bou