From: Dave Jones <davej@suse.de>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
"Eric W. Biederman" <ebiederm@xmission.com>,
Jeff Garzik <jgarzik@mandrakesoft.com>,
Anders Gustafsson <andersg@0x63.nu>,
arjanv@redhat.com, linux-kernel@vger.kernel.org, mochel@osdl.org
Subject: Re: [PATCH] devexit fixes in i82092.c
Date: Sun, 17 Mar 2002 00:15:33 +0100 [thread overview]
Message-ID: <20020317001533.E15296@suse.de> (raw)
In-Reply-To: <E16mMer-0007Q4-00@the-village.bc.nu> <Pine.LNX.4.33.0203161421240.8278-100000@home.transmeta.com>
In-Reply-To: <Pine.LNX.4.33.0203161421240.8278-100000@home.transmeta.com>
On Sat, Mar 16, 2002 at 02:26:23PM -0800, Linus Torvalds wrote:
> One question that hasn't come up: do we actually want to use the "remove"
> function for this, or have a separate shutdown function? Are there reasons
> to not use "remove" for shutdown?
Something that came to mind on reading this thread that I want
clarification on.. Take for example, the case of an IDE controller.
If on shutdown we walk the driverfs tree shutting things down,
it's going to power off its hard disks, then do whatever magic is
needed to the ide host bridge.
This makes sense for a shutdown, and suspend-to-disk, but not for
a reboot imo (senseless spinning down/up of drives).
So some means is probably going to be needed for drivers to
distinguish between a reboot & shutdown/suspend.
There may be other such devices too, but this was the more
obvious one that came to mind. Or am I way off base here?
--
| Dave Jones. http://www.codemonkey.org.uk
| SuSE Labs
next prev parent reply other threads:[~2002-03-16 23:16 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-16 0:57 [PATCH] devexit fixes in i82092.c Anders Gustafsson
2002-03-16 1:00 ` Linus Torvalds
2002-03-16 2:25 ` Jeff Garzik
2002-03-16 7:40 ` Linus Torvalds
2002-03-16 7:51 ` Keith Owens
2002-03-16 8:13 ` Linus Torvalds
2002-03-16 9:00 ` Jeff Garzik
2002-03-16 9:50 ` Keith Owens
2002-03-25 19:15 ` Patrick Mochel
2002-03-16 8:51 ` Jeff Garzik
2002-03-16 17:35 ` Alan Cox
2002-03-16 17:31 ` Jeff Garzik
2002-03-25 19:19 ` Patrick Mochel
2002-03-16 9:40 ` Arjan van de Ven
2002-03-22 15:47 ` Pavel Machek
2002-03-16 10:32 ` David Woodhouse
2002-03-16 19:27 ` Eric W. Biederman
2002-03-16 21:00 ` Alan Cox
2002-03-16 22:03 ` Eric W. Biederman
2002-03-16 22:28 ` Alan Cox
2002-03-16 22:16 ` Eric W. Biederman
2002-03-16 22:26 ` Linus Torvalds
2002-03-16 23:00 ` Eric W. Biederman
2002-03-16 23:15 ` Dave Jones [this message]
2002-03-21 15:12 ` Pavel Machek
2002-03-25 19:02 ` Patrick Mochel
-- strict thread matches above, loose matches on Subject: below --
2002-03-24 23:36 Alexander Stohr
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=20020317001533.E15296@suse.de \
--to=davej@suse.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=andersg@0x63.nu \
--cc=arjanv@redhat.com \
--cc=ebiederm@xmission.com \
--cc=jgarzik@mandrakesoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mochel@osdl.org \
--cc=torvalds@transmeta.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