From: David Howells <dhowells@redhat•com>
To: Sami Tolvanen <samitolvanen@google•com>
Cc: dhowells@redhat•com, Mark Brown <broonie@kernel•org>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>,
Petr Pavlu <petr.pavlu@suse•com>
Subject: Re: linux-next: manual merge of the keys-next tree with the modules tree
Date: Fri, 30 Jan 2026 21:56:59 +0000 [thread overview]
Message-ID: <2281244.1769810219@warthog.procyon.org.uk> (raw)
In-Reply-To: <CABCJKuf10mJnunp0gt0r-5Jnumss5LS1VjN51WQmJgnggE+BGA@mail.gmail.com>
Sami Tolvanen <samitolvanen@google•com> wrote:
> > Wouldn't that mean having to rebase before sending to Linus?
>
> Do you plan to send these to Linus for 7.0-rc1?
Yes, hopefully.
> The patches already depend on libcrypto-next landing first, right?
Yes - if that was the only thing, I'd just ask Linus to pull them after that.
> If the patches were last rebased 6h ago, I'm not sure if rebasing them on
> top of modules-next would significantly affect the linux-next soak time, but
> I'm fine either way.
Rebasing on modules-next wouldn't work unless modules-next has Eric's branch
merged in for the ML-DSA bits. I could maybe merge the two and rebase on
that, but I think Linus isn't keen on that.
David
next prev parent reply other threads:[~2026-01-30 21:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-30 17:20 linux-next: manual merge of the keys-next tree with the modules tree Mark Brown
2026-01-30 17:53 ` Sami Tolvanen
2026-01-30 17:57 ` David Howells
2026-01-30 18:10 ` Sami Tolvanen
2026-01-30 21:56 ` David Howells [this message]
2026-01-30 22:59 ` Sami Tolvanen
2026-01-30 18:06 ` Mark Brown
2026-01-30 18:13 ` Sami Tolvanen
2026-01-30 21:50 ` David Howells
2026-01-31 13:34 ` Mark Brown
2026-01-30 18:11 ` Mark Brown
2026-01-30 18:13 ` Sami Tolvanen
2026-01-30 18:18 ` Mark Brown
-- strict thread matches above, loose matches on Subject: below --
2026-02-03 19:18 Mark Brown
2026-02-03 19:26 ` Sami Tolvanen
2026-02-03 19:30 ` Mark Brown
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=2281244.1769810219@warthog.procyon.org.uk \
--to=dhowells@redhat$(echo .)com \
--cc=broonie@kernel$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=petr.pavlu@suse$(echo .)com \
--cc=samitolvanen@google$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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