From: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
To: "Bean Huo (beanhuo)" <beanhuo@micron.com>
Cc: Bart Van Assche <Bart.VanAssche@wdc.com>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
"vinholikatti@gmail.com" <vinholikatti@gmail.com>
Subject: Re: UFS utilities
Date: Tue, 5 Dec 2017 16:49:56 +0100 [thread overview]
Message-ID: <20171205154956.GB6264@kroah.com> (raw)
In-Reply-To: <95e2fba3abb6447ba741b6235dd2e375@SIWEX5A.sing.micron.com>
On Tue, Dec 05, 2017 at 03:44:19PM +0000, Bean Huo (beanhuo) wrote:
> Hi, greg k-h
>
> >
> >So what UFS commands are you missing that you need to see implemented?
> >
> >And again, have you checked the different forks of the driver?
> >
>
> Seems there is something misunderstood, I want to use UPIU, rather than CDB.
> Maybe it is not possible based on current UFS stacks. Of course, exactly,
> there is no missing SCSI command listed in UFS 2.1.
Again, have you looked at the different forks out there? I bet you can
already do this...
If not, I'm sure simple patches should be able to add the missing
functionality, it would be good to get a solid UFS driver one of these
days in the tree :)
thanks,
greg k-h
next prev parent reply other threads:[~2017-12-05 15:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-05 15:44 UFS utilities Bean Huo (beanhuo)
2017-12-05 15:49 ` gregkh [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-11-29 15:39 Bean Huo (beanhuo)
2017-11-29 16:19 ` Greg KH
2017-11-29 16:20 ` James Bottomley
2017-12-04 2:47 ` Kyuho Choi
2017-11-27 11:25 Bean Huo (beanhuo)
2017-11-27 11:40 ` Greg KH
2017-11-27 19:35 ` Bart Van Assche
2017-12-04 15:20 ` [EXT] " Bean Huo (beanhuo)
2017-12-05 22:22 ` Bart Van Assche
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=20171205154956.GB6264@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=Bart.VanAssche@wdc.com \
--cc=beanhuo@micron.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=stable@vger.kernel.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