From: Jorge Ramirez <jorge.ramirez@oss.qualcomm.com>
To: Jorge Ramirez <jorge.ramirez@oss.qualcomm.com>
Cc: Bean Huo <beanhuo@iokpp.de>,
James.Bottomley@hansenpartnership.com,
martin.petersen@oracle.com, alim.akhtar@samsung.com,
avri.altman@wdc.com, bvanassche@acm.org,
can.guo@oss.qualcomm.com, beanhuo@micron.com,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
jenswi@kernel.org, sumit.garg@oss.qualcomm.com
Subject: Re: [PATCH v1 0/2] ufs: rpmb: make RPMB usable with OP-TEE key derivation
Date: Wed, 5 Aug 2026 16:51:14 +0200 [thread overview]
Message-ID: <anNN4gZc9nvadHNs@trex> (raw)
In-Reply-To: <al3-w3j2-E2twGZj@trex>
On 20/07/26 12:56:03, Jorge Ramirez wrote:
> On 20/07/26 12:23:39, Bean Huo wrote:
> >
> > This is very strange, coverletter is v1, but the patches are v2?
>
> I messed up (manual edition of the letter) but the thread is proper
Any other comment on this set? Can we agree on the ABI change?
you can check the overall integration description here for more info:
https://github.com/OP-TEE/optee_os/pull/7881
next prev parent reply other threads:[~2026-08-05 14:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-20 9:16 [PATCH v1 0/2] ufs: rpmb: make RPMB usable with OP-TEE key derivation Jorge Ramirez-Ortiz
2026-07-20 9:16 ` [PATCH v2 1/2] ufs: rpmb: retry power-on UNIT ATTENTION on the RPMB WLUN Jorge Ramirez-Ortiz
2026-07-20 9:16 ` [PATCH v2 2/2] ufs: rpmb: use a fixed-length RPMB dev_id Jorge Ramirez-Ortiz
2026-07-20 10:23 ` [PATCH v1 0/2] ufs: rpmb: make RPMB usable with OP-TEE key derivation Bean Huo
2026-07-20 10:56 ` Jorge Ramirez
2026-08-05 14:51 ` Jorge Ramirez [this message]
2026-08-05 16:18 ` Bean Huo
2026-08-06 9:36 ` Jorge Ramirez
-- strict thread matches above, loose matches on Subject: below --
2026-07-16 8:37 Jorge Ramirez-Ortiz
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=anNN4gZc9nvadHNs@trex \
--to=jorge.ramirez@oss.qualcomm.com \
--cc=James.Bottomley@hansenpartnership.com \
--cc=alim.akhtar@samsung.com \
--cc=avri.altman@wdc.com \
--cc=beanhuo@iokpp.de \
--cc=beanhuo@micron.com \
--cc=bvanassche@acm.org \
--cc=can.guo@oss.qualcomm.com \
--cc=jenswi@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=sumit.garg@oss.qualcomm.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