From: Bart Van Assche <bvanassche@acm.org>
To: James Bottomley <James.Bottomley@HansenPartnership.com>,
Damien Le Moal <dlemoal@kernel.org>,
"Martin K . Petersen" <martin.petersen@oracle.com>,
linux-scsi@vger.kernel.org, linux-ide@vger.kernel.org
Subject: Re: [PATCH] scsi: sd: Introduce manage_shutdown device flag
Date: Thu, 26 Oct 2023 14:36:13 -0700 [thread overview]
Message-ID: <23f25e02-a451-4ad4-bb04-e3449a1e6dea@acm.org> (raw)
In-Reply-To: <c3dfca871ddddfeef004fdb74432630a148300f2.camel@HansenPartnership.com>
On 10/26/23 05:01, James Bottomley wrote:
> Heh, well, I was going to say we should still point to the doc, but I
> simply can't find it, so the above is perhaps the best we can do,
> thanks!
I think this should be documented in the Documentation/power directory.
After having taken another look at that directory, I see that there
is only detailed documentation and no overview documentation. Maybe I
overlooked something but I couldn't find an explanation of the system
suspend/resume nor of the runtime power management concepts in that
directory. My understanding is that system suspend/resume is about
system-wide power state changes (hibernation and suspend-to-RAM) and
also that runtime power management is about changing the power state of
a single device or bus if no activity has happened within a certain
time.
Bart.
next prev parent reply other threads:[~2023-10-26 21:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-25 7:01 [PATCH] scsi: sd: Introduce manage_shutdown device flag Damien Le Moal
2023-10-25 7:14 ` Damien Le Moal
2023-10-25 11:57 ` James Bottomley
2023-10-25 21:30 ` Damien Le Moal
2023-10-26 12:01 ` James Bottomley
2023-10-26 21:36 ` Bart Van Assche [this message]
2023-10-27 0:26 ` Damien Le Moal
2023-10-27 0:37 ` James Bottomley
2023-10-27 0:57 ` Martin K. Petersen
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=23f25e02-a451-4ad4-bb04-e3449a1e6dea@acm.org \
--to=bvanassche@acm.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=dlemoal@kernel.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.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