From: Nathan Chancellor <nathan@kernel.org>
To: Mark Brown <broonie@kernel.org>
Cc: linux-next@vger.kernel.org
Subject: Re: Adding clang-fixes tree to -next
Date: Fri, 17 Apr 2026 13:49:03 -0700 [thread overview]
Message-ID: <20260417204903.GA720760@ax162> (raw)
In-Reply-To: <e243a21a-8507-4bb5-b236-e2dd326672b4@sirena.org.uk>
On Fri, Apr 17, 2026 at 12:19:51PM +0100, Mark Brown wrote:
> I've added this from today. Given pending-fixes it might make sense to
> have two branches, one for the current merge window and one for the next
> merge window. An additional branch costs basically nothing if it's
> empty.
Yeah, that is fair. I do not anticipate having to carry many patches in
this tree, so we will see how it evolves. If I find myself needing to
accumulate a lot of material for the next merge window as opposed to the
current one, I will introduce a new branch and let you know.
Cheers,
Nathan
prev parent reply other threads:[~2026-04-17 20:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-16 23:22 Adding clang-fixes tree to -next Nathan Chancellor
2026-04-17 11:19 ` Mark Brown
2026-04-17 20:49 ` Nathan Chancellor [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=20260417204903.GA720760@ax162 \
--to=nathan@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox