[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1556139361.161891.140.camel@acm.org>
Date: Wed, 24 Apr 2019 13:56:01 -0700
From: Bart Van Assche <bvanassche@....org>
To: Pavel Machek <pavel@...x.de>, Jens Axboe <axboe@...nel.dk>,
jejb@...ux.ibm.com, martin.petersen@...cle.com, lduncan@...e.com,
hare@...e.com, mcgrof@...nel.org, jthumshirn@...e.de, hch@....de,
gregkh@...uxfoundation.org, dan.j.williams@...el.com
Cc: kernel list <linux-kernel@...r.kernel.org>, rjw@...ysocki.net,
linux-pm@...r.kernel.org, sfr@...b.auug.org.au,
linux-next@...r.kernel.org, hdegoede@...hat.com,
linux-ide@...r.kernel.org
Subject: Re: regression -next -- scsi: sd: Rely on the driver core for
asynchronous probing was Re: next-20190408..0418: Suspend/resume problems
on Thinkpad X60
On Wed, 2019-04-24 at 22:51 +0200, Pavel Machek wrote:
> Unfortunately, that one does not revert cleanly on top of -next.
Can you try the following:
git revert d16ece577bf2cee7f94bab75a0d967bcb89dd2a7 &&
git revert 21e6ba3f0e0257cce1a226c1f15e0a8ba4338ca3
I will see whether I can come up with a better way to analyze what is
going on. I had not expected that these patches would cause any suspend/
resume problems.
Bart.
Powered by blists - more mailing lists