[PATCH v4 0/2] kconfig: Remove the architecture specific config for AutoFDO and Propeller

[Nathan Chancellor]

On Thu, 04 Jun 2026 12:56:06 -0700, xur at google.com wrote:
> kconfig: Remove the architecture specific config for AutoFDO and Propeller
> 
> From: Rong Xu <xur at google.com>
> 
> ChangeLog:
>   V4: (1) updated docs for AutoFDO and Propeller
>       (2) moved .llvm_bb_addr_map sections grouping to the header file.
>       (3) use $(cc-option,...) for supported archs.
>   V3: (1) updated the base;
>       (2) changed vmlinux.lds.S for arm64 to avoid the warnings
>           from .llvm_bb_addr_map.
> 
> [...]

I took this series as is to move it along as a courtesy given the merge
window is approaching but I think it could have been organized better. I
would have done something like:

    Patch 1: Update AutoFDO documentation
    Patch 2: Update Propeller documentation
    Patch 3: Drop AutoFDO architecture specific configuration
    Patch 4: Factor out PROPELLER_DATA from x86 into vmlinux.lds.h
    Patch 5: Add PROPELLER_DATA to arm64's vmlinux.lds.S
    Patch 6: Drop Propeller architecture specific configuration and rely
             on compiler support alone

Try to stick to doing one thing per patch, it makes it much easier to
review and analyze in retrospect.

Applied to

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

Thanks!

[1/2] kconfig: Remove the architecture specific config for AutoFDO
      https://git.kernel.org/kbuild/c/e88b2fe8b9993
[2/2] kconfig: Remove the architecture specific config for Propeller
      https://git.kernel.org/kbuild/c/2566fa7b2f240

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