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... BR, Jarkko
