On Fri, 23 May 2025 at 18:02, Jarkko Sakkinen <jar...@kernel.org> wrote: > > On Thu, May 22, 2025 at 10:26:34AM +0200, Stefano Garzarella wrote: > > On Wed, 21 May 2025 at 18:42, Jarkko Sakkinen <jar...@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.
Sure, I'll send v6 after the merge window. Thanks, Stefano > > Thank you! > > > > > Thanks, > > Stefano > > BR, Jarkko >
