From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Bean Huo <beanhuo@iokpp.de>
Cc: 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,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 0/2] Changes for UFS advanced RPMB
Date: Wed, 30 Aug 2023 21:42:41 -0400 [thread overview]
Message-ID: <yq1il8wt2b7.fsf@ca-mkp.ca.oracle.com> (raw)
In-Reply-To: <20230809181847.102123-1-beanhuo@iokpp.de> (Bean Huo's message of "Wed, 9 Aug 2023 20:18:45 +0200")
Bean,
> 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
Applied to 6.6/scsi-staging, thanks!
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2023-08-31 1:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-09 18:18 [PATCH v1 0/2] Changes for UFS advanced RPMB 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 ` [PATCH v1 0/2] Changes for UFS advanced RPMB Bean Huo
2023-08-28 18:58 ` Bart Van Assche
2023-08-31 1:42 ` Martin K. Petersen [this message]
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=yq1il8wt2b7.fsf@ca-mkp.ca.oracle.com \
--to=martin.petersen@oracle.com \
--cc=alim.akhtar@samsung.com \
--cc=asutoshd@codeaurora.org \
--cc=avri.altman@wdc.com \
--cc=beanhuo@iokpp.de \
--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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.