From: Bart Van Assche <bvanassche@acm.org>
To: "haowenchao (C)" <haowenchao2@huawei.com>,
John Garry <john.g.garry@oracle.com>,
"James E . J . Bottomley" <jejb@linux.ibm.com>,
"Martin K . Petersen" <martin.petersen@oracle.com>,
Douglas Gilbert <dgilbert@interlog.com>,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: linfeilong@huawei.com, louhongxiang@huawei.com
Subject: Re: [PATCH 0/5]scsi:scsi_debug: Add error injection for single device
Date: Fri, 24 Mar 2023 09:01:58 -0700 [thread overview]
Message-ID: <0a152b0a-4fa9-c727-6e41-910e1eb71e2c@acm.org> (raw)
In-Reply-To: <0a6fc4bd-82a1-3200-3061-4634531b5a63@huawei.com>
On 3/23/23 20:42, haowenchao (C) wrote:
> If sysfs is not recommended, what about proc?
procfs is for process information and should not be used for any other
purpose.
Thanks,
Bart.
prev parent reply other threads:[~2023-03-24 16:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-23 11:55 [PATCH 0/5]scsi:scsi_debug: Add error injection for single device Wenchao Hao
2023-03-23 11:55 ` [PATCH 1/5] scsi:scsi_debug: Add sysfs interface to manage scsi devices' error injection Wenchao Hao
2023-03-23 11:55 ` [PATCH 2/5] scsi:scsi_debug: Define grammar to remove added " Wenchao Hao
2023-03-23 11:55 ` [PATCH 3/5] scsi:scsi_debug: timeout command if the error is injected Wenchao Hao
2023-03-23 11:56 ` [PATCH 4/5] scsi:scsi_debug: Return failed value " Wenchao Hao
2023-03-23 11:56 ` [PATCH 5/5] scsi:scsi_debug: set command's result and sense data " Wenchao Hao
2023-03-23 12:40 ` [PATCH 0/5]scsi:scsi_debug: Add error injection for single device John Garry
2023-03-23 13:13 ` haowenchao (C)
2023-03-23 16:25 ` John Garry
2023-03-23 17:24 ` Douglas Gilbert
2023-03-24 3:42 ` haowenchao (C)
2023-03-24 17:31 ` Douglas Gilbert
2023-03-25 3:23 ` haowenchao (C)
2023-03-24 3:42 ` haowenchao (C)
2023-03-24 16:01 ` Bart Van Assche [this message]
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=0a152b0a-4fa9-c727-6e41-910e1eb71e2c@acm.org \
--to=bvanassche@acm.org \
--cc=dgilbert@interlog.com \
--cc=haowenchao2@huawei.com \
--cc=jejb@linux.ibm.com \
--cc=john.g.garry@oracle.com \
--cc=linfeilong@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=louhongxiang@huawei.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