From: John Meneghini <jmeneghi@redhat.com>
To: "Kai Mäkisara (Kolumbus)" <kai.makisara@kolumbus.fi>
Cc: linux-scsi@vger.kernel.org, martin.petersen@oracle.com,
loberman@redhat.com
Subject: Re: [PATCH v3 4/4] scsi: st: Add sysfs file reset_blocked
Date: Fri, 31 Jan 2025 14:48:51 -0500 [thread overview]
Message-ID: <077ae4ca-e301-4b7c-b664-4b34941048ea@redhat.com> (raw)
In-Reply-To: <E86C013A-4C12-43E2-829D-7023F377A6B6@kolumbus.fi>
On 1/31/25 5:49 AM, "Kai Mäkisara (Kolumbus)" wrote:
> Combining the above and your suggestion, what about "position_lost_in_reset"
> or "pos_lost_in_reset"? (Whatever the name is, the user should check what
> has really happened. The name should point to the correct direction,
> but it should be short enough.)
I like it!
Reviewed-by: John Meneghini <jmeneghi@redhat.com>
Tested-by: John Meneghini <jmeneghi@redhat.com>
next prev parent reply other threads:[~2025-01-31 19:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-20 19:49 [PATCH v3 0/4] scsi: st: scsi_error: More reset patches Kai Mäkisara
2025-01-20 19:49 ` [PATCH v3 1/4] scsi: st: Restore some drive settings after reset Kai Mäkisara
2025-01-30 18:13 ` John Meneghini
2025-01-20 19:49 ` [PATCH v3 2/4] scsi: scsi_error: Add counters for New Media and Power On/Reset UNIT ATTENTIONs Kai Mäkisara
2025-01-30 18:13 ` John Meneghini
2025-01-20 19:49 ` [PATCH v3 3/4] scsi: st: scsi_device: Modify st.c to use the new scsi_error counters Kai Mäkisara
2025-01-30 18:18 ` John Meneghini
2025-01-20 19:49 ` [PATCH v3 4/4] scsi: st: Add sysfs file reset_blocked Kai Mäkisara
2025-01-30 18:27 ` John Meneghini
2025-01-31 10:49 ` "Kai Mäkisara (Kolumbus)"
2025-01-31 19:48 ` John Meneghini [this message]
2025-02-01 15:11 ` [PATCH v3b 4/4] scsi: st: Add sysfs file position_lost_in_reset Kai Mäkisara
2025-02-03 22:53 ` [PATCH v3 0/4] scsi: st: scsi_error: More reset patches Martin K. Petersen
2025-02-10 2:58 ` 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=077ae4ca-e301-4b7c-b664-4b34941048ea@redhat.com \
--to=jmeneghi@redhat.com \
--cc=kai.makisara@kolumbus.fi \
--cc=linux-scsi@vger.kernel.org \
--cc=loberman@redhat.com \
--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