From: Jorge Ramirez <jorge.ramirez@oss.qualcomm.com>
To: Bean Huo <beanhuo@iokpp.de>
Cc: Jorge Ramirez <jorge.ramirez@oss.qualcomm.com>,
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: Thu, 20 Aug 2026 09:54:45 +0200 [thread overview]
Message-ID: <aoayxeLGw50r-Dem@trex> (raw)
In-Reply-To: <ef5b527c25b9965296287498f7849f8b62533298.camel@iokpp.de>
On 17/08/26 16:46:52, Bean Huo wrote:
> On Mon, 2026-08-17 at 16:41 +0200, Jorge Ramirez wrote:
> > On 12/08/26 08:54:45, Jorge Ramirez wrote:
> > > On 06/08/26 11:36:54, Jorge Ramirez wrote:
> > > > On 05/08/26 18:18:31, Bean Huo wrote:
> > > > > On Wed, 2026-08-05 at 16:51 +0200, Jorge Ramirez wrote:
> > > > > > 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
> > > > >
> > > > >
> > > > > I would be ok on the ABI change, for this series kernel patch, patch
> > > > > [1/2] ok to
> > > > > me, just [2/2], I will add comment in the patch.
> > > >
> > > > ok. thanks Bean.
> > >
> > > could we follow up on this please?
> >
> >
> > just a reminder - there are op-tee/u-boot patches on the fly for the feature
> > that come together.
> > These changes are important to unblock
> >
> > tia
>
> I don't know what exactly you need, I have added comment in your patch of this
> version, you need to update it.
that is the thing Bean, I dont see those comments. let me reply to v2/2
next prev parent reply other threads:[~2026-08-20 7:54 UTC|newest]
Thread overview: 14+ 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-08-20 7:56 ` Jorge Ramirez
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
2026-08-05 16:18 ` Bean Huo
2026-08-06 9:36 ` Jorge Ramirez
2026-08-12 6:54 ` Jorge Ramirez
2026-08-17 14:41 ` Jorge Ramirez
2026-08-17 14:46 ` Bean Huo
2026-08-20 7:54 ` Jorge Ramirez [this message]
-- 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=aoayxeLGw50r-Dem@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