From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Avri Altman <avri.altman@wdc.com>
Cc: "James E.J. Bottomley" <jejb@linux.vnet.ibm.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
Evan Green <evgreen@chromium.org>, Bean Huo <beanhuo@micron.com>,
Pedro Sousa <pedrom.sousa@synopsys.com>,
Alim Akhtar <alim.akhtar@samsung.com>,
Avi Shchislowski <avi.shchislowski@wdc.com>,
Alex Lemberg <alex.lemberg@wdc.com>
Subject: Re: [REPOST PATCH v4 0/3] scsi: ufs-bsg: Add read descriptor
Date: Wed, 27 Feb 2019 09:00:38 -0500 [thread overview]
Message-ID: <yq136o9babd.fsf@oracle.com> (raw)
In-Reply-To: <1550646674-15258-1-git-send-email-avri.altman@wdc.com> (Avri Altman's message of "Wed, 20 Feb 2019 09:11:11 +0200")
Avri,
> UFS Protocol Information Units (UPIU) are UFS packets that travel
> between the host and the device on the UniPro bus. Our previous series
> added the capability to send UPIUs to the ufs driver. It does not
> cover all the possible UPIU types - we are mainly focused on device
> management, provisioning, testing and validation, so it covers UPIUs
> that falls in that box.
Applied to 5.1/scsi-queue, thanks!
--
Martin K. Petersen Oracle Linux Engineering
prev parent reply other threads:[~2019-02-27 14:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-20 7:11 [REPOST PATCH v4 0/3] scsi: ufs-bsg: Add read descriptor Avri Altman
2019-02-20 7:11 ` [REPOST PATCH v4 1/3] scsi: ufs-bsg: Change the calling convention for write descriptor Avri Altman
2019-02-20 7:11 ` [REPOST PATCH v4 2/3] scsi: ufs: Allow reading descriptor via raw upiu Avri Altman
2019-02-20 7:11 ` [REPOST PATCH v4 3/3] scsi: ufs-bsg: Allow reading descriptors Avri Altman
2019-02-26 10:59 ` [REPOST PATCH v4 0/3] scsi: ufs-bsg: Add read descriptor Avri Altman
2019-02-27 14:00 ` Martin K. Petersen [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=yq136o9babd.fsf@oracle.com \
--to=martin.petersen@oracle.com \
--cc=alex.lemberg@wdc.com \
--cc=alim.akhtar@samsung.com \
--cc=avi.shchislowski@wdc.com \
--cc=avri.altman@wdc.com \
--cc=beanhuo@micron.com \
--cc=evgreen@chromium.org \
--cc=jejb@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=pedrom.sousa@synopsys.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