From: Jarkko Sakkinen <jarkko@kernel.org>
To: Stefano Garzarella <sgarzare@redhat.com>
Cc: linuxppc-dev@lists.ozlabs.org, Peter Huewe <peterhuewe@gmx.de>,
Jens Wiklander <jens.wiklander@linaro.org>,
linux-integrity@vger.kernel.org,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
linux-arm-kernel@lists.infradead.org,
Nicolas Ferre <nicolas.ferre@microchip.com>,
Nicholas Piggin <npiggin@gmail.com>,
Sumit Garg <sumit.garg@kernel.org>,
James Bottomley <James.Bottomley@hansenpartnership.com>,
Claudiu Beznea <claudiu.beznea@tuxon.dev>,
Madhavan Srinivasan <maddy@linux.ibm.com>,
Jason Gunthorpe <jgg@ziepe.ca>,
linux-kernel@vger.kernel.org,
Christophe Leroy <christophe.leroy@csgroup.eu>,
Naveen N Rao <naveen@kernel.org>,
Michael Ellerman <mpe@ellerman.id.au>
Subject: Re: [PATCH v5 4/4] tpm/tpm_svsm: support TPM_CHIP_FLAG_SYNC
Date: Fri, 23 May 2025 19:02:03 +0300 [thread overview]
Message-ID: <aDCb-wkHGoLQ-IGg@kernel.org> (raw)
In-Reply-To: <CAGxU2F5zQJR4GvZ9ovtQBqMFGs-wBMoCRks=JYQ1JF6qMKK-6g@mail.gmail.com>
On Thu, May 22, 2025 at 10:26:34AM +0200, Stefano Garzarella wrote:
> On Wed, 21 May 2025 at 18:42, Jarkko Sakkinen <jarkko@kernel.org> wrote:
> >
> > On Wed, May 21, 2025 at 01:12:20PM +0300, Jarkko Sakkinen wrote:
> > > > I tried, but the last patch (this one) is based on the series merged
> > > > on the tip tree, where I introduced tpm_svsm.
> > > > I can see that series in linux-next merged with commit
> > > > 16a56ee59ab8ee05e67de35bbb5782ef9cfb4f07,
> > > > but I can't see it in your next tree [1].
> > > >
> > > > How do we proceed in such cases?
> > > >
> > > > Just to be sure, did I use the right tree?
> > >
> > > Thanks for the remark. Lemme check tonight. Hold on doing
> > > anything ;-) We'll get there...
> >
> > I just rebased my branches on top of latest from Linus. That is what I
> > need base PR also on, and:
> >
> > $ git show 16a56ee59ab8ee05e67de35bbb5782ef9cfb4f07
> > fatal: bad object 16a56ee59ab8ee05e67de35bbb5782ef9cfb4f07
> >
> > I'd use git cherry-pick on a range to take them from linux-next to a
> > mainline tip...
>
> I see, let me know if I can help in some way.
>
> We can also wait the next cycle if it simplifies your work, definitely
> no rush on my side.
Let's do it. At least it will then get a full round of testing before
ending up to a release.
Thank you!
>
> Thanks,
> Stefano
BR, Jarkko
next prev parent reply other threads:[~2025-05-23 17:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-14 13:46 [PATCH v5 0/4] tpm: add support for sync send() and use it in ftpm and svsm drivers Stefano Garzarella
2025-05-14 13:46 ` [PATCH v5 1/4] tpm: add bufsiz parameter in the .send callback Stefano Garzarella
2025-05-14 13:46 ` [PATCH v5 2/4] tpm: support devices with synchronous send() Stefano Garzarella
2025-05-14 13:46 ` [PATCH v5 3/4] tpm/tpm_ftpm_tee: support TPM_CHIP_FLAG_SYNC Stefano Garzarella
2025-05-29 2:03 ` Qunqin Zhao
2025-05-14 13:46 ` [PATCH v5 4/4] tpm/tpm_svsm: " Stefano Garzarella
2025-05-15 1:45 ` Jarkko Sakkinen
2025-05-20 16:06 ` Stefano Garzarella
2025-05-20 20:02 ` Jarkko Sakkinen
2025-05-21 7:13 ` Stefano Garzarella
2025-05-21 10:12 ` Jarkko Sakkinen
2025-05-21 16:41 ` Jarkko Sakkinen
2025-05-22 8:26 ` Stefano Garzarella
2025-05-23 16:02 ` Jarkko Sakkinen [this message]
2025-05-26 7:40 ` Stefano Garzarella
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=aDCb-wkHGoLQ-IGg@kernel.org \
--to=jarkko@kernel.org \
--cc=James.Bottomley@hansenpartnership.com \
--cc=alexandre.belloni@bootlin.com \
--cc=christophe.leroy@csgroup.eu \
--cc=claudiu.beznea@tuxon.dev \
--cc=jens.wiklander@linaro.org \
--cc=jgg@ziepe.ca \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maddy@linux.ibm.com \
--cc=mpe@ellerman.id.au \
--cc=naveen@kernel.org \
--cc=nicolas.ferre@microchip.com \
--cc=npiggin@gmail.com \
--cc=peterhuewe@gmx.de \
--cc=sgarzare@redhat.com \
--cc=sumit.garg@kernel.org \
/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.