From: Thorsten Blum <blum@kernel.org>
To: Mark Brown <broonie@kernel.org>
Cc: linux-next@vger.kernel.org
Subject: Re: linux-next: Add blum/linux.git for-next
Date: Fri, 13 Nov 2026 09:47:28 +0100 [thread overview]
Message-ID: <avbOoCsjrarxvY9g@kernel.org> (raw)
In-Reply-To: <0601ed55-a7fb-4f08-9e34-164103e140bb@sirena.org.uk>
On Thu, Nov 12, 2026 at 01:42:23PM +0000, Mark Brown wrote:
> On Thu, Nov 12, 2026 at 02:13:39PM +0100, Thorsten Blum wrote:
>
> > Could you please add
> >
> > https://git.kernel.org/pub/scm/linux/kernel/git/blum/linux.git for-next
> >
> > to linux-next?
>
> What is this branch intended to contain? Usually branches in -next are
> for specific trees or purposes, and this affects where they are included
> in the merge.
The branch is intended for cleanups and fixes across several subsystems
that have remained unmerged for some time.
It will contain only reviewed changes that are ready for integration
testing in linux-next ahead of the next merge window. I'll drop any
patches that maintainers pick up in the meantime.
I'm planning to send pull requests directly to Linus.
prev parent reply other threads:[~2026-11-13 8:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-12 13:13 linux-next: Add blum/linux.git for-next Thorsten Blum
2026-11-12 13:42 ` Mark Brown
2026-11-13 8:47 ` Thorsten Blum [this message]
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=avbOoCsjrarxvY9g@kernel.org \
--to=blum@kernel.org \
--cc=broonie@kernel.org \
--cc=linux-next@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.