From: Bean Huo <beanhuo@iokpp.de>
To: alim.akhtar@samsung.com, avri.altman@wdc.com,
asutoshd@codeaurora.org, jejb@linux.ibm.com,
martin.petersen@oracle.com, stanley.chu@mediatek.com,
beanhuo@micron.com, bvanassche@acm.org, tomas.winkler@intel.com,
cang@codeaurora.org, jonghwi.rha@samsung.com
Cc: linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 0/2] Changes for UFS advanced RPMB
Date: Sun, 27 Aug 2023 22:00:19 +0200 [thread overview]
Message-ID: <07a52c7643215c2dedd541df60c1a8499666f24a.camel@iokpp.de> (raw)
In-Reply-To: <20230809181847.102123-1-beanhuo@iokpp.de>
On Wed, 2023-08-09 at 20:18 +0200, Bean Huo wrote:
>
> Bean Huo (2):
> scsi: ufs: core: Add advanced RPMB support where UFSHCI 4.0 does
> not
> support EHS length in UTRD
> scsi: ufs: core: No need to update UPIU.header.flags and lun in
> advanced RPMB handler
>
> drivers/ufs/core/ufs_bsg.c | 3 +--
> drivers/ufs/core/ufshcd.c | 14 ++++++++++----
> 2 files changed, 11 insertions(+), 6 deletions(-)
>
Hi Martin and Bart,
what's opinion of this series of patch??
Bean
next prev parent reply other threads:[~2023-08-27 20:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-09 18:18 Bean Huo
2023-08-09 18:18 ` [PATCH v1 1/2] scsi: ufs: core: Add advanced RPMB support where UFSHCI 4.0 does not support EHS length in UTRD Bean Huo
2023-08-09 18:18 ` [PATCH v1 2/2] scsi: ufs: core: No need to update UPIU.header.flags and lun in advanced RPMB handler Bean Huo
2023-08-27 20:00 ` Bean Huo [this message]
2023-08-28 18:58 ` [PATCH v1 0/2] Changes for UFS advanced RPMB Bart Van Assche
2023-08-31 1:42 ` Martin K. Petersen
2023-09-05 10:18 ` Martin K. Petersen
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=07a52c7643215c2dedd541df60c1a8499666f24a.camel@iokpp.de \
--to=beanhuo@iokpp.de \
--cc=alim.akhtar@samsung.com \
--cc=asutoshd@codeaurora.org \
--cc=avri.altman@wdc.com \
--cc=beanhuo@micron.com \
--cc=bvanassche@acm.org \
--cc=cang@codeaurora.org \
--cc=jejb@linux.ibm.com \
--cc=jonghwi.rha@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=stanley.chu@mediatek.com \
--cc=tomas.winkler@intel.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®