Re: [PATCH v12 0/3] kbuild: distributed build support for Clang ThinLTO

On Fri, 29 May 2026 11:53:43 -0700, [email protected] wrote:
> kbuild: distributed build support for Clang ThinLTO
> 
> From: Rong Xu <[email protected]>
> 
> ChangeLog:
> 
> V12: Fixed an build error reported by Nathan Chancellor:
>      Reverted to v10 shell script based approach to get saved_c_flags.
> V11: Integrated feedback from Sashiko (Nathan Chancellor):
>      (1) Included modkern_cflags within the saved _c_flags.
>      (2) Replaced the shell command with $(saved_c_flags_$(<)).
>      (3) Refined the file matching for ar_vmlinux.a.
> V10: Fixed a minor build error in v9 and added comments.
> V9:  Fixed a minor build error.
> V8:  Disabled -always-rename-promoted-locals=false for the distrubute
>      mode, based on Yonghong and Nathan's comments.
> V7: (1) Resolved a conflict by rebasing to kbuild/kbuild-next-unstable.
>     (2) Separated the '--thin' to 'T' change into its own patch to
>         preserve Masahiro's original version.
> V6: Change '--thin' back to 'T' in Makefile.vmlinux_a to fix
>     reported the build error from old ar.
> V5: Handle single quote escaping in echo _c_flags to fix
>     Piotr Gorski's reported error.
> V4: This is based on the reimplementation provided by Masahiro Yamada
> on May 26. The difference is that this version now saves the compiler
> flags (_c_flags) from the Front-End (FE) compilation and re-uses them
> for the subsequent Back-End (BE) compilation.
> 
> [...]

As noted elsewhere in the thread, I squashed patches 1 and 2 to avoid
bisection issues.

Applied to

  https://git.kernel.org/pub/scm/linux/kernel/git/kbuild/linux.git kbuild-next

Thanks!

[1/2] kbuild: move vmlinux.a build rule to scripts/Makefile.vmlinux_a
      https://git.kernel.org/kbuild/c/9c72d26e9fe3b
[2/2] kbuild: distributed build support for Clang ThinLTO
      https://git.kernel.org/kbuild/c/9f2aee8f7d184

Please look out for regression or issue reports or other follow up
comments, as they may result in the patch/series getting dropped or
reverted. Patches applied to an "unstable" branch are accepted pending
wider testing in -next and any post-commit review; they will generally
be moved to the main branch in a week if no issues are found.

Best regards,
-- 
Cheers,
Nathan