linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Guenter Roeck <linux@roeck-us.net>,
	Thomas Gleixner <tglx@linutronix.de>,
	Kalesh Singh <kaleshsingh@google.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 5.11-rc1
Date: Mon, 28 Dec 2020 10:59:06 -0800	[thread overview]
Message-ID: <CAHk-=whHbfec+vxjpCXhRdSwA7uw6m0hS9kGqqJv6Af0EMFVBw@mail.gmail.com> (raw)
In-Reply-To: <20201228155149.GA197954@roeck-us.net>

On Mon, Dec 28, 2020 at 7:51 AM Guenter Roeck <linux@roeck-us.net> wrote:
>
> Build results:
>         total: 153 pass: 151 fail: 2

Thanks for doing these for the mainline rc's too. I've seen them for
the stable kernels, but it's lovely to see it for rc1.

> ERROR: modpost: "irq_check_status_bit" [drivers/perf/arm_spe_pmu.ko] undefined!
>
> Caused by: fdd029630434 ("genirq: Move status flag checks to core")

Ahh. Does it just need a

 EXPORT_SYMBOL_GPL(irq_check_status_bit);

in there? Because it looks like at least irq_is_percpu() and
irq_is_percpu_devid() are used in drivers/perf/ and can apparently be
modules.

Thomas?

> ia64:defconfig:
>
> include/linux/mmzone.h:1156:2: error: #error Allocator MAX_ORDER exceeds SECTION_SIZE
>
> and various related warnings.
>
> Caused by: 214496cb1870 ("ia64: make SPARSEMEM default and disable DISCONTIGMEM")
>
> Fix submitted ("ia64: fix build failure caused by memory model changes").

Ok, I won't worry about that one.

> qemu boot tests:
>
> arm:raspi2 hangs during boot.
>
> Caused by: ffdad793d579 ("irqchip/bcm2836: Make IPIs use handle_percpu_devid_irq()")
>
> Fix submitted ("irqchip/bcm2836: Fix IPI acknowledgement after conversion to
> handle_percpu_devid_irq").

Same.

> parisc: Failed to execute /sbin/init (error -12)
>
> Caused by: c49dd3401802 ("mm: speedup mremap on 1GB or larger regions")

Looks like Kalesh is looking at it.

I don't think that was supposed to matter at all on parisc, but
clearly something bad happened.

parsic doesn't even enable HAVE_MOVE_PMD, much less the new
HAVE_MOVE_PUD. Strange.

                 Linus

  reply	other threads:[~2020-12-28 19:00 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-28  0:04 Linux 5.11-rc1 Linus Torvalds
2020-12-28 15:51 ` Guenter Roeck
2020-12-28 18:59   ` Linus Torvalds [this message]
2020-12-28 19:37     ` Kalesh Singh
2020-12-28 20:02       ` Guenter Roeck
2020-12-30  1:59 ` linux-next: stats (Was: Linux 5.11-rc1) Stephen Rothwell
2020-12-28  7:30 Linux 5.11-rc1 Sedat Dilek
2020-12-28  8:04 ` Sedat Dilek
2020-12-28 15:18   ` Sedat Dilek
2020-12-28 19:40   ` Linus Torvalds
2020-12-28 20:05     ` Sedat Dilek
2021-01-01 16:14     ` Pavel Machek
2021-01-01 18:55       ` Sedat Dilek
2021-01-01 22:31         ` Sedat Dilek
2021-01-02  7:51         ` Masahiro Yamada
2021-01-02  9:13           ` Sedat Dilek
2021-01-02 11:05             ` Bernd Petrovitsch
2021-01-02 11:26               ` Sedat Dilek
2021-01-02 11:57                 ` Bernd Petrovitsch
2021-01-02 12:11                   ` Sedat Dilek
2021-01-03 17:39               ` David Laight
2021-01-02 15:30           ` Masahiro Yamada
2020-12-28 15:25 ` Sedat Dilek
2020-12-28 19:45   ` Linus Torvalds
2020-12-28 20:08     ` Sedat Dilek
2021-01-02 23:26 Ilkka Prusi
2021-01-03 17:45 ` David Laight
2021-01-04  1:47   ` Adam Borowski

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='CAHk-=whHbfec+vxjpCXhRdSwA7uw6m0hS9kGqqJv6Af0EMFVBw@mail.gmail.com' \
    --to=torvalds@linux-foundation.org \
    --cc=kaleshsingh@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=tglx@linutronix.de \
    /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;
as well as URLs for NNTP newsgroup(s).