Adjusting clang-fixes branches

Adjusting clang-fixes branches

[Nathan Chancellor]

Hi Mark,

Could you please update the clang-fixes trees to use

  https://git.kernel.org/pub/scm/linux/kernel/git/nathan/linux.git clang-fixes-for-current

for pending fixes and

  https://git.kernel.org/pub/scm/linux/kernel/git/nathan/linux.git clang-fixes-for-next

for patches destined for the next merge window? Thanks!

-- 
Cheers,
Nathan

Re: Adjusting clang-fixes branches

[Mark Brown]

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

On Tue, Sep 08, 2026 at 05:15:31PM -0700, Nathan Chancellor wrote:

> Could you please update the clang-fixes trees to use

>   https://git.kernel.org/pub/scm/linux/kernel/git/nathan/linux.git clang-fixes-for-current

> for pending fixes and

This is a new tree, I have added it from today.

>   https://git.kernel.org/pub/scm/linux/kernel/git/nathan/linux.git clang-fixes-for-next
> 
> for patches destined for the next merge window? Thanks!

This was the existing tree, I moved it.

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