Re: [PATCH 0/3] hexagon: Fix build error with CONFIG_STACKDEPOT and select CONFIG_ARCH_WANT_LD_ORPHAN_WARN

[Nathan Chancellor <nathan@kernel.org>]

On 5/20/2021 6:12 PM, Nathan Chancellor wrote:
> Hi all,
> 
> This series fixes an error with ARCH=hexagon that was pointed out by
> the patch "mm/slub: use stackdepot to save stack trace in objects",
> which is in -mm/-next.
> 
> The first patch fixes that error by handling the '.irqentry.text' and
> '.softirqentry.text' sections.
> 
> The second patch switches Hexagon over to the common DISCARDS macro,
> which should have been done when Hexagon was merged into the tree to
> match commit 023bf6f1b8bf ("linker script: unify usage of discard
> definition").
> 
> The third patch selects CONFIG_ARCH_WANT_LD_ORPHAN_WARN so that
> something like this does not happen again.
> 
> Nathan Chancellor (3):
>    hexagon: Handle {,SOFT}IRQENTRY_TEXT in linker script
>    hexagon: Use common DISCARDS macro
>    hexagon: Select ARCH_WANT_LD_ORPHAN_WARN
> 
>   arch/hexagon/Kconfig              | 1 +
>   arch/hexagon/kernel/vmlinux.lds.S | 9 +++------
>   2 files changed, 4 insertions(+), 6 deletions(-)
> 
> 
> base-commit: 7a42b92b6d30c3f09629c7d5ada9e3de2aba01af
> 

Brian, did you have any comments on this series? ARCH=hexagon defconfig 
is currently broken in -next, it would be a real shame if this continued 
to regress after you just got Hexagon building in mainline. These 
patches seem like they would be worthy of a 5.13 pull request. 
Otherwise, Andrew could pick them up with your ack and stick them in 
front of "mm/slub: use stackdepot to save stack trace in objects" so 
that there is no build regression.

Cheers,
Nathan