From: Christoph Hellwig <hch@infradead.org>
To: Avri Altman <Avri.Altman@wdc.com>
Cc: Evan Green <evgreen@chromium.org>,
Doug Anderson <dianders@chromium.org>,
"martin.petersen@oracle.com" <martin.petersen@oracle.com>,
Vinayak Holikatti <vinholikatti@gmail.com>,
"jejb@linux.vnet.ibm.com" <jejb@linux.vnet.ibm.com>,
Stanislav Nijnikov <Stanislav.Nijnikov@wdc.com>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Bart Van Assche <Bart.VanAssche@wdc.com>,
"adrian.hunter@intel.com" <adrian.hunter@intel.com>,
sayali <sayalil@codeaurora.org>
Subject: Re: [PATCH v4] scsi: ufs: Make sysfs attributes writable
Date: Thu, 27 Sep 2018 07:01:33 -0700 [thread overview]
Message-ID: <20180927140133.GA22096@infradead.org> (raw)
In-Reply-To: <SN6PR04MB4925DAB09EED762CDCCBBF47FC140@SN6PR04MB4925.namprd04.prod.outlook.com>
On Thu, Sep 27, 2018 at 06:32:47AM +0000, Avri Altman wrote:
> Also, in this context there is the series in
> https://www.spinics.net/lists/linux-scsi/msg123479.html
> which allows to send UPIUs via a bsg device.
>
> It's not a provisioning series per-se like Evan's and Sayali's.
> It covers the provisioning functionality,
> But also allow to send task management UPIU, and UIC commands,
> Which can be used for testing and validation.
And as someone having been involved with review of a few different
UFS provisioning bits this is what I think we should be merging.
Instead of being in a rat race of adding ever new sysfs or configfs
attributes for things that don't matter to normal driver operation
I'd rather have a relatively clean pass through interface and move
policy to userspace. Especially given that there are plenty of
vendor specific commands at these levels as well.
next prev parent reply other threads:[~2018-09-27 14:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-08 22:44 [PATCH v4] scsi: ufs: Make sysfs attributes writable Evan Green
2018-08-09 8:14 ` Stanislav Nijnikov
2018-08-22 11:00 ` Adrian Hunter
2018-09-04 10:27 ` Adrian Hunter
2018-09-25 18:40 ` Doug Anderson
2018-09-26 1:08 ` Martin K. Petersen
2018-09-26 1:46 ` Doug Anderson
2018-09-26 17:41 ` Evan Green
2018-09-27 6:32 ` Avri Altman
2018-09-27 14:01 ` Christoph Hellwig [this message]
2018-09-27 23:16 ` Evan Green
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=20180927140133.GA22096@infradead.org \
--to=hch@infradead.org \
--cc=Avri.Altman@wdc.com \
--cc=Bart.VanAssche@wdc.com \
--cc=Stanislav.Nijnikov@wdc.com \
--cc=adrian.hunter@intel.com \
--cc=dianders@chromium.org \
--cc=evgreen@chromium.org \
--cc=jejb@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=sayalil@codeaurora.org \
--cc=vinholikatti@gmail.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