All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bart Van Assche <bvanassche@acm.org>
To: Pavel Machek <pavel@denx.de>, Jens Axboe <axboe@kernel.dk>,
	jejb@linux.ibm.com, martin.petersen@oracle.com, lduncan@suse.com,
	hare@suse.com, mcgrof@kernel.org, jthumshirn@suse.de, hch@lst.de,
	gregkh@linuxfoundation.org, dan.j.williams@intel.com
Cc: kernel list <linux-kernel@vger.kernel.org>,
	rjw@rjwysocki.net, linux-pm@vger.kernel.org,
	sfr@canb.auug.org.au, linux-next@vger.kernel.org,
	hdegoede@redhat.com, linux-ide@vger.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
Date: Wed, 24 Apr 2019 13:56:01 -0700	[thread overview]
Message-ID: <1556139361.161891.140.camel@acm.org> (raw)
In-Reply-To: <20190424205150.GA4582@amd>

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.

WARNING: multiple messages have this Message-ID (diff)
From: Bart Van Assche <bvanassche@acm.org>
To: Pavel Machek <pavel@denx.de>, Jens Axboe <axboe@kernel.dk>,
	jejb@linux.ibm.com, martin.petersen@oracle.com, lduncan@suse.com,
	hare@suse.com, mcgrof@kernel.org, jthumshirn@suse.de, hch@lst.de,
	gregkh@linuxfoundation.org, dan.j.williams@intel.com
Cc: kernel list <linux-kernel@vger.kernel.org>,
	rjw@rjwysocki.net, linux-pm@vger.kernel.org,
	sfr@canb.auug.org.au, linux-next@vger.kernel.org,
	hdegoede@redhat.com, linux-ide@vger.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
Date: Wed, 24 Apr 2019 13:56:01 -0700	[thread overview]
Message-ID: <1556139361.161891.140.camel@acm.org> (raw)
Message-ID: <20190424205601.QA6ibrABWZuDS0GdNawdJZnZl8aaxwMMYXJuHvULnWE@z> (raw)
In-Reply-To: <20190424205150.GA4582@amd>

On Wed, 2019-04-24 at 22:51 +-0200, Pavel Machek wrote:
+AD4 Unfortunately, that one does not revert cleanly on top of -next.

Can you try the following:

git revert d16ece577bf2cee7f94bab75a0d967bcb89dd2a7 +ACYAJg
  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.

  reply	other threads:[~2019-04-24 20:56 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-08 17:39 next-20190408: Suspend/resume problems on Thinkpad X60 Pavel Machek
2019-04-12 10:28 ` Pavel Machek
2019-04-23 10:22   ` next-20190408..0418: " Pavel Machek
2019-04-23 13:55     ` Jens Axboe
2019-04-24  8:26       ` Pavel Machek
2019-04-24  9:54       ` Pavel Machek
2019-04-24 10:48         ` Pavel Machek
2019-04-24 20:21           ` Pavel Machek
2019-04-24 20:48             ` regression -next -- scsi: sd: Rely on the driver core for asynchronous probing was " Pavel Machek
2019-04-24 20:51               ` Pavel Machek
2019-04-24 20:56                 ` Bart Van Assche [this message]
2019-04-24 20:56                   ` Bart Van Assche
2019-04-25  7:33                   ` Pavel Machek
2019-04-25 13:35                     ` Bart Van Assche
2019-04-26 10:32                       ` Pavel Machek
2019-04-26 14:58                         ` Bart Van Assche
2019-04-26 14:58                           ` Bart Van Assche
2019-04-26 17:59                           ` Pavel Machek
2019-04-23 14:09     ` Bart Van Assche
2019-04-24 10:17       ` Pavel Machek
2019-04-24 22:34         ` Bart Van Assche
2019-04-24 22:34           ` Bart Van Assche

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=1556139361.161891.140.camel@acm.org \
    --to=bvanassche@acm.org \
    --cc=axboe@kernel.dk \
    --cc=dan.j.williams@intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=hare@suse.com \
    --cc=hch@lst.de \
    --cc=hdegoede@redhat.com \
    --cc=jejb@linux.ibm.com \
    --cc=jthumshirn@suse.de \
    --cc=lduncan@suse.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=mcgrof@kernel.org \
    --cc=pavel@denx.de \
    --cc=rjw@rjwysocki.net \
    --cc=sfr@canb.auug.org.au \
    /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.