linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Tudor Ambarus <tudor.ambarus@microchip.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Guenter Roeck <linux@roeck-us.net>,
	Saravana Kannan <saravanak@google.com>,
	Stephen Boyd <sboyd@kernel.org>
Subject: Re: Linux 5.13-rc1
Date: Mon, 10 May 2021 15:20:41 -0700	[thread overview]
Message-ID: <CAHk-=whcSbW+CprMV4=F2QQG_yuoD9kJRi2Ec2XP8Hu1ixkYOA@mail.gmail.com> (raw)
In-Reply-To: <20210510193924.GA3929105@roeck-us.net>

Just adding Greg & co explicitly to the participants to make sure
they're aware of this..

Greg? This came through your driver core tree.

                Linus

On Mon, May 10, 2021 at 12:39 PM Guenter Roeck <linux@roeck-us.net> wrote:
>
> On Mon, May 10, 2021 at 12:01:00PM -0700, Linus Torvalds wrote:
> > On Sun, May 9, 2021 at 7:54 PM Guenter Roeck <linux@roeck-us.net> wrote:
> > >
> > > Qemu test results:
> > >         total: 462 pass: 460 fail: 2
> > > Failed tests:
> > >         arm:raspi2:multi_v7_defconfig:net,usb:bcm2836-rpi-2-b:initrd
> > >         arm:raspi2:multi_v7_defconfig:sd:net,usb:bcm2836-rpi-2-b:rootfs
> > >
> > > The raspi2 problem (a crash in of_clk_add_hw_provider) is well known.
> > > It was introduced with commit 6579c8d97ad7 ("clk: Mark fwnodes when
> > > their clock provider is added"). Unfortunately it appears that there
> > > is still no agreement on how to fix it.
> >
> > Hmm. I see
> >
> >     https://lore.kernel.org/linux-acpi/20210426065618.588144-1-tudor.ambarus@microchip.com/
> >
> > and don't see any objections to that version.
> >
> > Does that fix it for you too?
> >
>
> Yes, it does. It was submitted ~2 weeks ago, so I have no idea what its
> status might be (it is not in the most recent -next). I just sent a
> Tested-by:, figuring that it can't hurt.
>
> Guenter

  reply	other threads:[~2021-05-10 22:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-09 21:43 Linux 5.13-rc1 Linus Torvalds
2021-05-10  2:54 ` Guenter Roeck
2021-05-10 19:01   ` Linus Torvalds
2021-05-10 19:39     ` Guenter Roeck
2021-05-10 22:20       ` Linus Torvalds [this message]
2021-05-11  6:48         ` Greg Kroah-Hartman
2021-05-10 17:54 ` Naresh Kamboju
2021-05-10 18:55   ` Linus Torvalds

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-=whcSbW+CprMV4=F2QQG_yuoD9kJRi2Ec2XP8Hu1ixkYOA@mail.gmail.com' \
    --to=torvalds@linux-foundation.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=saravanak@google.com \
    --cc=sboyd@kernel.org \
    --cc=tudor.ambarus@microchip.com \
    /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).