From: Oliver Neukum <oneukum@suse.de>
To: Charles Chiou <ch1102chiou@gmail.com>
Cc: Christoph Hellwig <hch@infradead.org>,
JBottomley@parallels.com, ed.lin@promise.com,
grace.chang@tw.promise.com, linus.chen@tw.promise.com,
victor.p@promise.com, linux-scsi@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 4/4 v4] scsi:stex.c Add S3/S4 support
Date: Tue, 16 Dec 2014 10:34:10 +0100 [thread overview]
Message-ID: <1418722450.2448.3.camel@linux-0dmf.site> (raw)
In-Reply-To: <548FCDC8.1010900@gmail.com>
On Tue, 2014-12-16 at 14:14 +0800, Charles Chiou wrote:
> From f9d84df080c16097218092630db9b5df31d487b5 Mon Sep 17 00:00:00 2001
> From: Charles Chiou <charles.chiou@tw.promise.com>
> Date: Fri, 7 Nov 2014 10:15:18 +0800
> Subject: [PATCH 4/4] scsi:stex.c Add S3/S4 support
>
> Add S3/S4 support, add .suspend and .resume function in pci_driver.
>
> Pegasus need 30~40 seconds to boot up. We don't want to OS wait
> in .resume function. Create a thread to handle device boot up.
I am sorry to be obnoxious, but this patch raises another
question. What happens if the the system is suspended again
while the work scheduled in resume is still running?
Furthermore, what happens in the case of a PCI hotunplug while
the work is still scheduled?
Regards
Oliver
next prev parent reply other threads:[~2014-12-16 9:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-16 6:14 [PATCH 4/4 v4] scsi:stex.c Add S3/S4 support Charles Chiou
2014-12-16 9:34 ` Oliver Neukum [this message]
2014-12-18 3:09 ` Charles Chiou
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=1418722450.2448.3.camel@linux-0dmf.site \
--to=oneukum@suse.de \
--cc=JBottomley@parallels.com \
--cc=ch1102chiou@gmail.com \
--cc=ed.lin@promise.com \
--cc=grace.chang@tw.promise.com \
--cc=hch@infradead.org \
--cc=linus.chen@tw.promise.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=victor.p@promise.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox