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

Quoted 8 lines

So my request is to:
1. Include the two new branches.
2. Remove the old branch.
[1] https://lore.kernel.org/linux-integrity/[email protected]/
BR, Jarkko

Linus-next is now being taken care of by Mark Brown (cc'd).

Signature · 2 lines

Cheers,
Stephen Rothwell

Jarkko Sakkinen

author

2026-04-22 09:34 UTC #2 lore raw

Quoted 16 lines · Stephen Rothwell

Hi Jarkko,
Quoted 13 lines · On Tue, 21 Apr 2026 21:19:14 +0300 Jarkko Sakkinen <[email protected]> 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:

Quoted 8 lines

Quoted 6 lines
1. Include the two new branches.
2. Remove the old branch.
[1] https://lore.kernel.org/linux-integrity/[email protected]/
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.

Quoted 3 lines

Signature · 2 lines
Cheers,
Stephen Rothwell

BR, Jarkko

Mark Brown

maintainer

2026-04-22 12:11 UTC #3 lore raw

Quoted 6 lines · Jarkko Sakkinen

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.

I didn't see this mail until after I'd started things running for today but I've now updated the config so the two new trees should appear from tomorrow as tpmdd-keys and tpmdd-tpm, and the old tpmdd tree has been removed.

Thanks for adding your subsystem tree as a participant of linux-next. As you may know, this is not a judgement of your code. The purpose of linux-next is for integration testing and to lower the impact of conflicts between subsystems in the next merge window.

You will need to ensure that the patches/commits in your tree/series have been:
* submitted under GPL v2 (or later) and include the Contributor's Signed-off-by,
* posted to the relevant mailing list,
* reviewed by you (or another maintainer of your subsystem tree),
* successfully unit tested, and
* destined for the current or next Linux merge window.

Basically, this should be just what you would send to Linus (or ask him to fetch). It is allowed to be rebased if you deem it necessary.

Jarkko Sakkinen

author

2026-04-22 13:46 UTC #4 lore raw

Quoted 6 lines · Mark Brown

Quoted 3 lines · Jarkko Sakkinen
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).

Quoted 7 lines

Quoted 2 lines
for-next-tpm and for-next-keys will replace 'next', which I will delete after the change is effective.
I didn't see this mail until after I'd started things running for today but I've now updated the config so the two new trees should appear from tomorrow as tpmdd-keys and tpmdd-tpm, and the old tpmdd tree has been removed.

AFAIC, this was fast response time :-) (less than 24h)

Quoted 5 lines

Thanks for adding your subsystem tree as a participant of linux-next. As you may know, this is not a judgement of your code. The purpose of linux-next is for integration testing and to lower the impact of conflicts between subsystems in the next merge window.

Quoted 8 lines

You will need to ensure that the patches/commits in your tree/series have been:
* submitted under GPL v2 (or later) and include the Contributor's Signed-off-by,
* posted to the relevant mailing list,
* reviewed by you (or another maintainer of your subsystem tree),
* successfully unit tested, and
* destined for the current or next Linux merge window.

Sure.

Quoted 3 lines

Basically, this should be just what you would send to Linus (or ask him to fetch). It is allowed to be rebased if you deem it necessary.

My old topology caused more noise than necessary, and was getting difficult to manage, as each pull request required reorg of commits in my next branch, every time I prepared a PR.

Thanks for your trouble.

BR, Jarkko