From: Pavel Machek <pavel@ucw.cz>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
gregkh@linuxfoundation.org, kyle@kernel.org,
akpm@linux-foundation.org, mmarek@suse.com,
yamada.masahiro@socionext.com, dwmw2@infradead.org,
markus@trippelsdorf.de, torvalds@linux-foundation.org
Cc: kernel list <linux-kernel@vger.kernel.org>,
len.brown@intel.com, linux-pm@vger.kernel.org
Subject: Re: [regression] Re: Thinkpad T40p: suspend to ram stopped working sometime before 4.14
Date: Mon, 25 Dec 2017 00:22:13 +0100 [thread overview]
Message-ID: <20171224232213.GA23103@amd> (raw)
In-Reply-To: <20171224223739.GA24747@amd>
[-- Attachment #1: Type: text/plain, Size: 875 bytes --]
Hi!
> > And it seems bad commit is
> >
> > commit 5620a0d1aacd554ebebcff373e31107bb1ef7769
> > Author: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> > Date: Thu Sep 14 14:23:01 2017 -0700
> >
> > firmware: delete in-kernel firmware
> >
> > Unfortuantely, it does not revert cleanly.
>
> I can't, because there's df85b2d767aad90fd2746f993fcd66dd322768f8 on
> top of it, partialy reverting it. Seems like 5620 was causing problems
> for other people before.
>
> And then there's huge mega-patch called "license cleanup" on top of
> that, which changes 11100 files (!) and makes work harder still.
>
> Can we go for full revert?
And revert indeed fixes suspend on T40p on v4.15-rc5.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2017-12-24 23:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-24 11:49 Thinkpad T40p: suspend to ram stopped working sometime before 4.14 Pavel Machek
2017-12-24 12:04 ` Rafael J. Wysocki
2017-12-24 15:22 ` Pavel Machek
2017-12-24 15:36 ` Pavel Machek
2017-12-24 18:17 ` [regression] " Pavel Machek
2017-12-24 22:37 ` Pavel Machek
2017-12-24 23:22 ` Pavel Machek [this message]
2017-12-25 8:47 ` Markus Trippelsdorf
2017-12-25 9:54 ` Pavel Machek
2017-12-25 10:05 ` Markus Trippelsdorf
2017-12-28 12:19 ` Pavel Machek
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=20171224232213.GA23103@amd \
--to=pavel@ucw.cz \
--cc=akpm@linux-foundation.org \
--cc=dwmw2@infradead.org \
--cc=gregkh@linuxfoundation.org \
--cc=kyle@kernel.org \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=markus@trippelsdorf.de \
--cc=mmarek@suse.com \
--cc=rjw@rjwysocki.net \
--cc=torvalds@linux-foundation.org \
--cc=yamada.masahiro@socionext.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.