linux-next changes on my tree

[Jarkko Sakkinen <jarkko@kernel.org>]

Hi,

First I want to apologize for messing up with PRs for 7.1 [1]. I've
taken steps to sanitize my branching and the changes are now reflected
to -next:

commit 3ee56e5cf8afb875beab59e42e0b69cdb31050ab
Merge: e77ce03e10ba 4fb4ce024d06
Author: Mark Brown <broonie@kernel.org>
Date:   Thu Apr 23 13:26:01 2026 +0100

    Merge branch 'for-next-keys' of
    https://git.kernel.org/pub/scm/linux/kernel/git/jarkko/linux-tpmdd.git

commit e77ce03e10baf7b84d169efcaa497861dc9a07bf
Merge: c6391bbee383 949692da7211
Author: Mark Brown <broonie@kernel.org>
Date:   Thu Apr 23 13:26:00 2026 +0100

    Merge branch 'for-next-tpm' of
    https://git.kernel.org/pub/scm/linux/kernel/git/jarkko/linux-tpmdd.git

I'm now travelling right now in Budapest but will be back in Finland
tomorrow, and will retry my PRs then.

Paul, I promised to look into [2] this week but unfortunately it is
delayed +1 but is on my TODO list for next week along with couple
of other kernel review/testing backlog items :-) Hope you understand.

[1] https://lore.kernel.org/linux-integrity/aeVSbVIFaCDRXf7C@kernel.org/T/#t
    Yes, and I know late cc-tagging was also additional reason for
    NAK, can't blame branching on that. I did also execute stupid shit
    to add in.
[2] https://lore.kernel.org/all/ad--R8KaGgucLxmH@kernel.org/

BR, Jarkko