mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Paul Zimmerman <pauldzim@gmail.com>
To: linux@roeck-us.net
Cc: linux-kernel@vger.kernel.org, torvalds@linux-foundation.org
Subject: Re: Linux 5.11-rc4
Date: Mon, 18 Jan 2021 20:35:53 -0700	[thread overview]
Message-ID: <20210119033553.39607-1-pauldzim@gmail.com> (raw)
In-Reply-To: <20210118223520.GA193902@roeck-us.net>

On Mon, Jan 18, 2021 at 14:35:20 -0800, Guenter Roeck wrote:
> On Sun, Jan 17, 2021 at 04:56:46PM -0800, Linus Torvalds wrote:
>> Things continue to look fairly normal for this release: 5.11-rc4 is
>> solidly average in size, and nothing particularly scary stands out.
>> 
>> In the diff itself, the new ampere modesetting support shows up fairly
>> clearly - it's one of those hardware enablement things that should be
>> entirely invisible to people who don't have that hardware, but it does
>> end up being about a fifth of the whole rc4 patch.
>> 
>> If you ignore that oddity, the rest looks pretty normal, with random
>> patches all over, and a lot of it being quite small. All the usual
>> suspects: drivers (gpu, sound, rdma, md, networking..) arch updates
>> (arm64, risc-v, x86), fiesystems (ext4, nfs, btrfs), core networking,
>> documentation and tooling. And just random fixes.
>> 
>
>Here are the test results:
>
>Build results:
>	total: 153 pass: 151 fail: 2
>Failed builds:
>	arm64:allmodconfig
>	ia64:defconfig
>Qemu test results:
>	total: 430 pass: 428 fail: 2
>Failed tests:
>	arm:raspi2:multi_v7_defconfig:bcm2836-rpi-2-b:initrd
>	arm:raspi2:multi_v7_defconfig:sd:bcm2836-rpi-2-b:rootfs
>
>Same old ...

Hi Guenter,

Can you give a link to the problem that Qemu is having with RPI2?
Maybe I can take a look at it.

Thanks,
Paul

  reply	other threads:[~2021-01-19  3:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-18  0:56 Linus Torvalds
2021-01-18 22:35 ` Guenter Roeck
2021-01-19  3:35   ` Paul Zimmerman [this message]
2021-01-19  3:48     ` Guenter Roeck

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=20210119033553.39607-1-pauldzim@gmail.com \
    --to=pauldzim@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --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 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®