Re: [PATCH 1/7] consolidate per-arch stack overflow debugging options

From: James Hogan
Date: Tue May 07 2013 - 18:53:41 EST


On 7 May 2013 21:46, Dave Hansen <dave@xxxxxxxx> wrote:
>
> From: Dave Hansen <dave@xxxxxxxxxxxxxxxxxx>
>
> Several architectures have similar stack debugging config options.
> They all pretty much do the same thing, some with slightly
> differing help text.
>
> This patch changes the architectures to instead enable a Kconfig
> boolean, and then use that boolean in the generic Kconfig.debug
> to present the actual menu option. This removes a bunch of
> duplication and adds consistency across arches.
>
> Signed-off-by: Dave Hansen <dave@xxxxxxxxxxxxxxxxxx>
> Reviewed-by: H. Peter Anvin <hpa@xxxxxxxxx>
> Reviewed-by: James Hogan <james.hogan@xxxxxxxxxx>
> Acked-by: Chris Metcalf <cmetcalf@xxxxxxxxxx> [for tile]
> Signed-off-by: Dave Hansen <dave.hansen@xxxxxxxxx>
> ---
>
> linux.git-davehans/arch/blackfin/Kconfig | 1 +
> linux.git-davehans/arch/blackfin/Kconfig.debug | 7 -------
> linux.git-davehans/arch/frv/Kconfig | 1 +
> linux.git-davehans/arch/frv/Kconfig.debug | 4 ----
> linux.git-davehans/arch/m32r/Kconfig | 1 +
> linux.git-davehans/arch/m32r/Kconfig.debug | 7 -------
> linux.git-davehans/arch/mips/Kconfig | 1 +
> linux.git-davehans/arch/mips/Kconfig.debug | 9 ---------
> linux.git-davehans/arch/mn10300/Kconfig | 1 +
> linux.git-davehans/arch/mn10300/Kconfig.debug | 4 ----
> linux.git-davehans/arch/powerpc/Kconfig | 1 +
> linux.git-davehans/arch/powerpc/Kconfig.debug | 7 -------
> linux.git-davehans/arch/tile/Kconfig | 1 +
> linux.git-davehans/arch/tile/Kconfig.debug | 7 -------
> linux.git-davehans/arch/x86/Kconfig | 1 +
> linux.git-davehans/arch/x86/Kconfig.debug | 10 ----------
> linux.git-davehans/lib/Kconfig.debug | 21 +++++++++++++++++++++
> 17 files changed, 29 insertions(+), 55 deletions(-)

Now that metag, arc, and openrisc architectures are merged, maybe you
could convert them too?

Cheers
James
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/