From: Nathan Chancellor <nathan@kernel.org>
To: Mark Brown <broonie@kernel.org>
Cc: linux-next@vger.kernel.org
Subject: Adding clang-fixes tree to -next
Date: Thu, 16 Apr 2026 16:22:11 -0700 [thread overview]
Message-ID: <20260416232211.GA97229@ax162> (raw)
Hi Mark,
Could you please add
https://git.kernel.org/pub/scm/linux/kernel/git/nathan/linux.git clang-fixes-for-next
to -next? It will typically include build fixes for clang targeting the
current development cycle but may occasionally include things for the
next merge window, depending on size and timing.
If there are any issues or questions, please let me know.
Cheers,
Nathan
next reply other threads:[~2026-04-16 23:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-16 23:22 Nathan Chancellor [this message]
2026-04-17 11:19 ` Adding clang-fixes tree to -next Mark Brown
2026-04-17 20:49 ` Nathan Chancellor
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=20260416232211.GA97229@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