Adding clang-fixes tree to -next

Adding clang-fixes tree to -next

[Nathan Chancellor]

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

Re: Adding clang-fixes tree to -next

[Mark Brown]

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

On Thu, Apr 16, 2026 at 04:22:11PM -0700, Nathan Chancellor wrote:

> 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.

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.

Thanks for adding your subsystem tree as a participant of linux-next.  As
you may know, this is not a judgement of your code.  The purpose of
linux-next is for integration testing and to lower the impact of
conflicts between subsystems in the next merge window.

You will need to ensure that the patches/commits in your tree/series have
been:
     * submitted under GPL v2 (or later) and include the Contributor's
        Signed-off-by,
     * posted to the relevant mailing list,
     * reviewed by you (or another maintainer of your subsystem tree),
     * successfully unit tested, and
     * destined for the current or next Linux merge window.

Basically, this should be just what you would send to Linus (or ask him
to fetch).  It is allowed to be rebased if you deem it necessary.

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

Re: Adding clang-fixes tree to -next

[Nathan Chancellor]

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