Subject: Re: next sync updates

From: Jarkko Sakkinen <[email-masked]>
Date: Wed, 22 Apr 2026 12:34:04 +0300

On Wed, Apr 22, 2026 at 09:35:28AM +1000, Stephen Rothwell wrote:
> Hi Jarkko,
> 
> On Tue, 21 Apr 2026 21:19:14 +0300 Jarkko Sakkinen <[email-masked]> wrote:
> >
> > In order to address in long-term the issues reported by Linus [1], in
> > addition to improving my workflows, I've create two branches:
> > 
> > 1. https://git.kernel.org/pub/scm/linux/kernel/git/jarkko/linux-tpmdd.git/log/?h=for-next-tpm
> > 2. https://git.kernel.org/pub/scm/linux/kernel/git/jarkko/linux-tpmdd.git/log/?h=for-next-keys
> > 
> > These will replace the currently mirrored branch:
> > 
> > https://git.kernel.org/pub/scm/linux/kernel/git/jarkko/linux-tpmdd.git/log/?h=next
> > 
> > So my request is to:
> > 
> > 1. Include the two new branches.
> > 2. Remove the old branch.
> > 
> > [1] https://lore.kernel.org/linux-integrity/[email-masked]/
> > 
> > BR, Jarkko
> 
> Linus-next is now being taken care of by Mark Brown (cc'd).

Thank you for forwarding this.

Mark, the goal is to address the main problem Linus was complaining
about i.e., late rewrites of Git trees (aside from late cc stable
rewrite, which could have been prevented).

for-next-tpm and for-next-keys will replace 'next', which I will
delete after the change is effective.

> -- 
> Cheers,
> Stephen Rothwell

BR, Jarkko