From: Greg KH <greg@kroah.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Mike Rapoport <rppt@linux.ibm.com>,
stable <stable@vger.kernel.org>,
Chris Wilson <chris@chris-wilson.co.uk>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 5.11-rc5
Date: Wed, 27 Jan 2021 10:38:53 +0100 [thread overview]
Message-ID: <YBE0rYEf6Uc6HbK8@kroah.com> (raw)
In-Reply-To: <CAHk-=wgKbFUUhkRKvh4SHQcsUyG_kraLOTBLHUhc4GQ58ANBEw@mail.gmail.com>
On Tue, Jan 26, 2021 at 10:45:10AM -0800, Linus Torvalds wrote:
> On Tue, Jan 26, 2021 at 8:25 AM Mike Rapoport <rppt@linux.ibm.com> wrote:
> >
> > On Mon, Jan 25, 2021 at 09:46:19PM +0000, Chris Wilson wrote:
> > >
> > > CI does confirm that the revert of d3921cb8be29 brings the machines back
> > > to life.
> >
> > I still cannot see what could possibly go wrong, so let's revert
> > d3921cb8be29 for now and I'll continue to work with Chris to debug this.
>
> Ok, reverted in my tree.
>
> And added stable to the cc, so that they know not to pick up that
> commit d3921cb8be29, despite it being marked for stable.
I've dropped it from the 5.10.y queue now, thanks for letting me know.
greg k-h
next prev parent reply other threads:[~2021-01-27 9:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAHk-=wgmJ0q1URHrOb-2iCOdZ8gYybiH6LY2Gq7cosXu6kxAnA@mail.gmail.com>
[not found] ` <161160687463.28991.354987542182281928@build.alporthouse.com>
[not found] ` <CAHk-=wh23BXwBwBgPmt9h2EJztnzKKf=qr5r=B0Hr6BGgZ-QDA@mail.gmail.com>
[not found] ` <20210125213348.GB196782@linux.ibm.com>
[not found] ` <161161117911.29150.13853544418926100149@build.alporthouse.com>
[not found] ` <20210126162440.GC196782@linux.ibm.com>
2021-01-26 18:45 ` Linux 5.11-rc5 Linus Torvalds
2021-01-27 9:38 ` Greg KH [this message]
2021-02-04 18:19 ` Mike Rapoport
2021-02-04 18:32 ` Linus Torvalds
2021-02-05 6:54 ` 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=YBE0rYEf6Uc6HbK8@kroah.com \
--to=greg@kroah.com \
--cc=akpm@linux-foundation.org \
--cc=chris@chris-wilson.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=rppt@linux.ibm.com \
--cc=stable@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox