From: Randy Dunlap <rdunlap@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-um <linux-um@lists.infradead.org>
Subject: Re: linux-next: Tree for Sep 19 (UML)
Date: Tue, 19 Sep 2023 08:42:07 -0700 [thread overview]
Message-ID: <04b8a6de-2b20-4488-b20f-c8a8f6001fd2@infradead.org> (raw)
In-Reply-To: <20230919163728.78432283@canb.auug.org.au>
On 9/18/23 23:37, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20230918:
>
> New tree: kvm-ppc
>
> The mm tree gained a boot warning for which I reverted 5 commits.
>
> Non-merge commits (relative to Linus' tree): 5750
> 3717 files changed, 446028 insertions(+), 107378 deletions(-)
>
> ----------------------------------------------------------------------------
>
on i386 or x86_64:
../arch/x86/um/../kernel/module.c: In function 'execmem_arch_params':
../arch/x86/um/../kernel/module.c:54:50: error: implicit declaration of function 'kaslr_enabled'; did you mean 'kasan_enabled'? [-Werror=implicit-function-declaration]
54 | if (IS_ENABLED(CONFIG_RANDOMIZE_BASE) && kaslr_enabled())
| ^~~~~~~~~~~~~
| kasan_enabled
git blames this on:
commit 12633d679796
Author: Stephen Rothwell <sfr@canb.auug.org.au>
Date: Tue Sep 19 15:14:03 2023 +1000
Revert "arch: make execmem setup available regardless of CONFIG_MODULES"
This reverts commit 3300c3af20090ff5e03e5c4bf2ef2cfaa03d4e9b.
--
~Randy
next prev parent reply other threads:[~2023-09-19 15:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-19 6:37 linux-next: Tree for Sep 19 Stephen Rothwell
2023-09-19 15:42 ` Randy Dunlap [this message]
2023-09-19 21:18 ` linux-next: Tree for Sep 19 (UML) Nick Desaulniers
2023-09-19 23:18 ` Stephen Rothwell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=04b8a6de-2b20-4488-b20f-c8a8f6001fd2@infradead.org \
--to=rdunlap@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-um@lists.infradead.org \
--cc=sfr@canb.auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®