From: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org
Subject: Re: Linux 5.18-rc4
Date: Mon, 25 Apr 2022 10:50:57 +0100 [thread overview]
Message-ID: <YmZvAUakbWnyQEqa@debian> (raw)
In-Reply-To: <CAHk-=whmtHMzjaVUF9bS+7vE_rrRctcCTvsAeB8fuLYcyYLN-g@mail.gmail.com>
Hi Linus,
On Sun, Apr 24, 2022 at 03:22:59PM -0700, Linus Torvalds wrote:
> Fairly slow and calm week - which makes me just suspect that the other
> shoe will drop at some point.
>
> But maybe things are just going really well this release. It's bound
> to happen _occasionally_, after all.
My last night's mainline build failed for arm.
Build was with af2d861d4cd2 ("Linux 5.18-rc4").
imxrt_defconfig -> failed
lpc18xx_defconfig -> failed
mps2_defconfig -> failed
stm32_defconfig -> failed
vf610m4_defconfig -> failed
arm-linux-gnueabi-ld: mm/page_alloc.o: in function `alloc_large_system_hash':
page_alloc.c:(.init.text+0xe7c): undefined reference to `vmalloc_huge'
--
Regards
Sudip
next prev parent reply other threads:[~2022-04-25 9:51 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-24 22:22 Linux 5.18-rc4 Linus Torvalds
2022-04-25 7:32 ` Build regressions/improvements in v5.18-rc4 Geert Uytterhoeven
2022-04-25 7:42 ` Geert Uytterhoeven
2022-04-25 9:50 ` Sudip Mukherjee [this message]
2022-04-25 21:27 ` Linux 5.18-rc4 Andrew Morton
2022-04-25 21:42 ` Linus Torvalds
2022-04-25 15:03 ` Guenter Roeck
2022-04-27 17:59 ` Ammar Faizi
2022-04-27 18:31 ` Linus Torvalds
[not found] ` <87r1414y5v.fsf@email.froward.int.ebiederm.org>
2022-06-06 18:28 ` Linus Torvalds
2022-06-06 19:19 ` John Johansen
2022-06-06 19:47 ` Linus Torvalds
2022-06-06 20:23 ` Matthew Wilcox
2022-06-06 21:00 ` John Johansen
2022-06-13 22:48 ` Matthew Wilcox
2022-06-21 20:27 ` John Johansen
2022-07-13 9:37 ` Ammar Faizi
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=YmZvAUakbWnyQEqa@debian \
--to=sudipm.mukherjee@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=torvalds@linux-foundation.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.