From: Bart Van Assche <bvanassche@acm.org>
To: j-young.choi@samsung.com, ALIM AKHTAR <alim.akhtar@samsung.com>,
"avri.altman@wdc.com" <avri.altman@wdc.com>,
"jejb@linux.ibm.com" <jejb@linux.ibm.com>,
"martin.petersen@oracle.com" <martin.petersen@oracle.com>,
"beanhuo@micron.com" <beanhuo@micron.com>,
"adrian.hunter@intel.com" <adrian.hunter@intel.com>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 2/2] scsi: ufs: wb: Add Manual Flush sysfs
Date: Thu, 7 Jul 2022 15:45:08 -0700 [thread overview]
Message-ID: <e8981c50-2c80-94cc-8d19-f26440ce3ec0@acm.org> (raw)
In-Reply-To: <20220701074814epcms2p8bfb6c00d7364aa704e2d6e60088e6a22@epcms2p8>
On 7/1/22 00:48, Jinyoung CHOI wrote:
>
The subject of this email is incomplete. "sysfs" should be changed into
"sysfs attribute".
Additional, the use of the word "manual" in the subject seems weird to
me. I think the term "explicit" from the UFS specification describes the
purpose of the new sysfs attribute better.
Thanks,
Bart.
prev parent reply other threads:[~2022-07-07 22:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20220701074420epcms2p4c4a6a016c7070d5dfa279fc4607caa95@epcms2p4>
2022-07-01 7:44 ` [PATCH v3 0/2] scsi: ufs: wb: Add sysfs and cleanup Jinyoung CHOI
[not found] ` <CGME20220701074420epcms2p4c4a6a016c7070d5dfa279fc4607caa95@epcms2p5>
2022-07-01 7:46 ` [PATCH v3 1/2] scsi: ufs: wb: renaming & cleanups functions Jinyoung CHOI
2022-07-03 13:00 ` Avri Altman
[not found] ` <CGME20220701074420epcms2p4c4a6a016c7070d5dfa279fc4607caa95@epcms2p2>
2022-07-04 2:44 ` Jinyoung CHOI
2022-07-07 22:28 ` Bart Van Assche
[not found] ` <CGME20220701074420epcms2p4c4a6a016c7070d5dfa279fc4607caa95@epcms2p8>
2022-07-01 7:48 ` [PATCH v3 2/2] scsi: ufs: wb: Add Manual Flush sysfs Jinyoung CHOI
2022-07-03 13:08 ` Avri Altman
2022-07-07 22:45 ` 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=e8981c50-2c80-94cc-8d19-f26440ce3ec0@acm.org \
--to=bvanassche@acm.org \
--cc=adrian.hunter@intel.com \
--cc=alim.akhtar@samsung.com \
--cc=avri.altman@wdc.com \
--cc=beanhuo@micron.com \
--cc=j-young.choi@samsung.com \
--cc=jejb@linux.ibm.com \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®