From: Randy Dunlap <firstname.lastname@example.org>
To: Stephen Rothwell <email@example.com>,
Linux Next Mailing List <firstname.lastname@example.org>
Cc: Linux Kernel Mailing List <email@example.com>,
Masami Hiramatsu <firstname.lastname@example.org>,
Steven Rostedt <email@example.com>
Subject: Re: linux-next: Tree for Oct 25 (bootconfig: xbc_alloc_mem())
Date: Mon, 25 Oct 2021 20:20:02 -0700 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
On 10/25/21 2:49 AM, Stephen Rothwell wrote:
> Hi all,
> There seems to be something amiss with cnosole output in today's release
> (at least on my ppc qemu boot tests).
> Changes since 20211022:
> The nds32 tree gained a conflict against the kbuild tree.
> The qcom tree gained a build failure so I used the version from
> The nfsd tree gained a conflict against the nfs tree.
> The sound-asoc tree gained a build failure so I used the version from
> The block tree gained a conflict against Linus' tree.
> The regulator tree lost its build failure.
> The tip tree lost its build failure but gained another for which I
> applied a patch.
> The ftrace tree gained a conflict against the parisc-hd tree.
> The kvm tree gained a conflict against the tip tree.
> The kspp-gustavo tree still had one of its build failures for which I
> reverted a commit. It also gained a conflict against the ftrace tree.
> The akpm-current tree gained a conflict against the ftrace tree.
> Non-merge commits (relative to Linus' tree): 10130
> 9510 files changed, 594184 insertions(+), 218643 deletions(-)
> I have created today's linux-next tree at
> (patches at http://www.kernel.org/pub/linux/kernel/next/ ). If you
> are tracking the linux-next tree using git, you should not use "git pull"
> to do so as that will try to merge the new linux-next release with the
> old one. You should use "git fetch" and checkout or reset to the new
> You can see which trees have been included by looking in the Next/Trees
> file in the source. There are also quilt-import.log and merge.log
> files in the Next directory. Between each merge, the tree was built
> with a ppc64_defconfig for powerpc, an allmodconfig for x86_64, a
> multi_v7_defconfig for arm and a native build of tools/perf. After
> the final fixups (if any), I do an x86_64 modules_install followed by
> builds for x86_64 allnoconfig, powerpc allnoconfig (32 and 64 bit),
> ppc44x_defconfig, allyesconfig and pseries_le_defconfig and i386, sparc
> and sparc64 defconfig and htmldocs. And finally, a simple boot test
> of the powerpc pseries_le_defconfig kernel in qemu (with and without
> kvm enabled).
> Below is a summary of the state of the merge.
> I am currently merging 340 trees (counting Linus' and 92 trees of bug
> fix patches pending for the current merge release).
> Stats about the size of the tree over time can be seen at
> http://neuling.org/linux-next-size.html .
> Status of my local build tests will be at
> http://kisskb.ellerman.id.au/linux-next . If maintainers want to give
> advice about cross compilers/configs that work, we are always open to add
> more builds.
> Thanks to Randy Dunlap for doing many randconfig builds. And to Paul
> Gortmaker for triage and bug fixes.
WARNING: modpost: vmlinux.o(.text.unlikely+0x29b16): Section mismatch in reference from the function xbc_alloc_mem() to the function .init.text:memblock_alloc_try_nid()
The function xbc_alloc_mem() references
the function __init memblock_alloc_try_nid().
This is often because xbc_alloc_mem lacks a __init
annotation or the annotation of memblock_alloc_try_nid is wrong.
Looks like lib/bootconfig.c::xbc_alloc_mem() should be marked
as __init (when it's built for KERNEL).
next prev parent reply other threads:[~2021-10-26 3:20 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-25 9:49 linux-next: Tree for Oct 25 Stephen Rothwell
2021-10-25 20:50 ` linux-next: Tree for Oct 25 (drivers/platform/x86/amd-pmc.c) Randy Dunlap
2021-10-25 21:29 ` Hans de Goede
2021-10-25 21:32 ` Limonciello, Mario
2021-10-26 7:55 ` Hans de Goede
2021-10-25 22:11 ` linux-next: Tree for Oct 25 Dmitry Osipenko
2021-10-26 1:28 ` Ming Lei
2021-10-26 8:40 ` Dmitry Osipenko
2021-10-26 3:20 ` Randy Dunlap [this message]
2021-10-26 5:11 ` linux-next: Tree for Oct 25 (bootconfig: xbc_alloc_mem()) Stephen Rothwell
2021-10-27 11:42 ` linux-next: Tree for Oct 25 Stephen Rothwell
2021-10-27 12:54 ` Greg Kroah-Hartman
2021-10-28 1:51 ` Xianting Tian
2021-10-28 4:51 ` Stephen Rothwell
2021-10-28 7:59 ` Xianting Tian
2021-10-28 12:48 ` Stephen Rothwell
2021-10-28 12:54 ` Xianting Tian
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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;
as well as URLs for NNTP newsgroup(s).