From: Damien Le Moal <dlemoal@kernel.org>
To: "Martin K . Petersen" <martin.petersen@oracle.com>,
James Bottomley <James.Bottomley@HansenPartnership.com>,
linux-scsi@vger.kernel.org, linux-ide@vger.kernel.org
Cc: Bart Van Assche <bvanassche@acm.org>, Phillip Susi <phill@thesusis.net>
Subject: [PATCH v2 0/2] Fix runtime suspended device resume
Date: Tue, 21 Nov 2023 07:56:29 +0900 [thread overview]
Message-ID: <20231120225631.37938-1-dlemoal@kernel.org> (raw)
The first patch changes the use of the bool type back to the regular
unsigned:1 for the manage_xxx scsi device flags. This is marked as a fix
and CC-stable to avoid issues with later eventual fixes in this area.
The second patch addresses an issue with system resume with devices that
were runtime suspended. For ATA devices, this leads to a disk still
being reported as suspended while it is in fact spun up due to how ATA
resume is done (port reset).
Changes from v1:
- Fixed typos in patch 2 commit message.
Damien Le Moal (2):
scsi: Change scsi device boolean fields to single bit flags
scsi: sd: fix system start for ATA devices
drivers/ata/libata-scsi.c | 9 +++++++--
drivers/firewire/sbp2.c | 6 +++---
drivers/scsi/sd.c | 9 ++++++++-
include/scsi/scsi_device.h | 12 +++++++++---
4 files changed, 27 insertions(+), 9 deletions(-)
--
2.42.0
next reply other threads:[~2023-11-20 22:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-20 22:56 Damien Le Moal [this message]
2023-11-20 22:56 ` [PATCH v2 1/2] scsi: Change scsi device boolean fields to single bit flags Damien Le Moal
2023-11-21 9:28 ` Niklas Cassel
2023-11-20 22:56 ` [PATCH v2 2/2] scsi: sd: fix system start for ATA devices Damien Le Moal
2023-11-25 2:53 ` [PATCH v2 0/2] Fix runtime suspended device resume 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=20231120225631.37938-1-dlemoal@kernel.org \
--to=dlemoal@kernel.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=bvanassche@acm.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=phill@thesusis.net \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).