From: Nigel Cunningham <ncunningham@users.sourceforge.net>
To: Andrew Morton <akpm@osdl.org>
Cc: john@grabjohn.com,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: PATCH: Shutdown IDE before powering off.
Date: Thu, 22 Jan 2004 22:10:57 +1300 [thread overview]
Message-ID: <1074762656.12774.33.camel@laptop-linux> (raw)
In-Reply-To: <20040122004554.26536158.akpm@osdl.org>
[-- Attachment #1: Type: text/plain, Size: 617 bytes --]
Hi.
On Thu, 2004-01-22 at 21:45, Andrew Morton wrote:
> A couple of thoughts come to mind:
>
> a) Don't do it if the user typed reboot - only do it if we're powering down.
You'd think a parameter called shutdown would do that :>
> b) Try to do a cache flush instead. If that fails (do we know?) then
> power down the disk instead.
We're calling drivers_suspend and then sys_reboot for powering down, and
only calling sys_reboot when rebooting. Shouldn't cache flushes already
be happening?
Regards,
Nigel
--
My work on Software Suspend is graciously brought to you by
LinuxFund.org.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-01-22 9:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-22 1:42 PATCH: Shutdown IDE before powering off Nigel Cunningham
2004-01-22 7:49 ` Andrew Morton
2004-01-22 8:13 ` John Bradford
2004-01-22 8:26 ` Nigel Cunningham
2004-01-22 8:45 ` Andrew Morton
2004-01-22 9:10 ` Nigel Cunningham [this message]
2004-01-22 16:02 ` Jeff Garzik
2004-01-22 17:13 ` Bartlomiej Zolnierkiewicz
2004-01-22 10:08 ` John Bradford
2004-01-22 19:19 ` James H. Cloos Jr.
2004-01-22 19:36 ` Nigel Cunningham
2004-01-22 19:52 ` James H. Cloos Jr.
2004-01-22 21:07 ` Jeff Garzik
[not found] <1gC8S-6UB-5@gated-at.bofh.it>
[not found] ` <1gIHq-3JU-23@gated-at.bofh.it>
[not found] ` <1gPzb-1OM-17@gated-at.bofh.it>
[not found] ` <1gQET-2Qn-9@gated-at.bofh.it>
2004-03-11 21:46 ` Karol Kozimor
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=1074762656.12774.33.camel@laptop-linux \
--to=ncunningham@users.sourceforge.net \
--cc=akpm@osdl.org \
--cc=john@grabjohn.com \
--cc=linux-kernel@vger.kernel.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