public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Jarkko Sakkinen <jarkko@kernel.org>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Mark Brown <broonie@kernel.org>
Subject: Re: next sync updates
Date: Wed, 22 Apr 2026 09:35:28 +1000	[thread overview]
Message-ID: <20260422093528.42562dac@canb.auug.org.au> (raw)
In-Reply-To: <aee_mCW8p2J6IbIO@kernel.org>

[-- Attachment #1: Type: text/plain, Size: 870 bytes --]

Hi Jarkko,

On Tue, 21 Apr 2026 21:19:14 +0300 Jarkko Sakkinen <jarkko@kernel.org> 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/aeVSbVIFaCDRXf7C@kernel.org/
> 
> BR, Jarkko

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

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2026-04-21 23:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-21 18:19 next sync updates Jarkko Sakkinen
2026-04-21 23:35 ` Stephen Rothwell [this message]
2026-04-22  9:34   ` Jarkko Sakkinen
2026-04-22 12:10     ` Mark Brown
2026-04-22 13:46       ` Jarkko Sakkinen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20260422093528.42562dac@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=broonie@kernel.org \
    --cc=jarkko@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox