stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Biedl <linux-kernel.bfrz@manchmal.in-ulm.de>
To: Greg KH <greg@kroah.com>
Cc: Jack Wang <jack.wang.usish@gmail.com>,
	stable <stable@vger.kernel.org>,
	iommu@lists.linux-foundation.org
Subject: Re: 5.10.37 won't boot on my system, but 5.10.36 with same config does
Date: Tue, 18 May 2021 00:30:15 +0200	[thread overview]
Message-ID: <1621290515@msgid.manchmal.in-ulm.de> (raw)
In-Reply-To: <YKJ5ysGAuI32Jpn6@kroah.com>

[-- Attachment #1: Type: text/plain, Size: 538 bytes --]

Greg KH wrote...

> On Mon, May 17, 2021 at 02:45:01PM +0200, Jack Wang wrote:

> > So it's caused by this commit[1], and it should be fixed by latest
> > 5.10.38-rc1 https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git/log/?h=linux-5.10.y
> > [1]https://lore.kernel.org/stable/20210515132855.4bn7ve2ozvdhpnj4@nabokov.fritz.box/
> 
> Hopefully the "real" 5.10.38-rc1 release that is out now should fix
> this.  If not, please let us know.

Good news: Fixed with that "real" 5.10.38-rc1.

    Christoph

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2021-05-17 22:30 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-16 11:34 5.10.37 won't boot on my system, but 5.10.36 with same config does Charles Wright
2021-05-16 16:00 ` Christoph Biedl
2021-05-17 10:01   ` Greg KH
2021-05-17 11:38     ` Christoph Biedl
2021-05-17 11:45       ` Greg KH
2021-05-17 11:51       ` Christoph Biedl
2021-05-17 12:17         ` Jack Wang
2021-05-17 12:25           ` Christoph Biedl
2021-05-17 12:45             ` Jack Wang
2021-05-17 14:12               ` Greg KH
2021-05-17 22:30                 ` Christoph Biedl [this message]
2021-05-18  5:48                   ` Greg KH

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=1621290515@msgid.manchmal.in-ulm.de \
    --to=linux-kernel.bfrz@manchmal.in-ulm.de \
    --cc=greg@kroah.com \
    --cc=iommu@lists.linux-foundation.org \
    --cc=jack.wang.usish@gmail.com \
    --cc=stable@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).