From: Chris Metcalf <cmetcalf@tilera.com>
To: Dave Hansen <dave@linux.vnet.ibm.com>
Cc: linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org,
Mike Frysinger <vapier@gentoo.org>,
David Howells <dhowells@redhat.com>,
Hirokazu Takata <takata@linux-m32r.org>,
Ralf Baechle <ralf@linux-mips.org>,
Koichi Yasutake <yasutake.koichi@jp.panasonic.com>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Paul Mackerras <paulus@samba.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
x86@kernel.org, uclinux-dist-devel@blackfin.uclinux.org
Subject: Re: [PATCH] consolidate per-arch stack overflow debugging options
Date: Fri, 11 Jan 2013 12:36:47 -0500 [thread overview]
Message-ID: <50F04DAF.5040104@tilera.com> (raw)
In-Reply-To: <20130111170043.D7CC39DC@kernel.stglabs.ibm.com>
On 1/11/2013 12:00 PM, Dave Hansen wrote:
> I'm looking for some Acked-bys on this from the various arch
> maintainers that it affects. I'd like to send it up to Linus
> in the next merge window. This is part of a larger series to
> clean up the "Kernel Hacking" menu:
>
> https://lkml.org/lkml/2012/12/17/306
>
> --
>
> 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.
>
Acked-by: Chris Metcalf <cmetcalf@tilera.com> [for tile]
--
Chris Metcalf, Tilera Corp.
http://www.tilera.com
WARNING: multiple messages have this Message-ID (diff)
From: Chris Metcalf <cmetcalf@tilera.com>
To: Dave Hansen <dave@linux.vnet.ibm.com>
Cc: <linux-kernel@vger.kernel.org>, <linux-arch@vger.kernel.org>,
Mike Frysinger <vapier@gentoo.org>,
David Howells <dhowells@redhat.com>,
Hirokazu Takata <takata@linux-m32r.org>,
Ralf Baechle <ralf@linux-mips.org>,
Koichi Yasutake <yasutake.koichi@jp.panasonic.com>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Paul Mackerras <paulus@samba.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
<x86@kernel.org>, <uclinux-dist-devel@blackfin.uclinux.org>
Subject: Re: [PATCH] consolidate per-arch stack overflow debugging options
Date: Fri, 11 Jan 2013 12:36:47 -0500 [thread overview]
Message-ID: <50F04DAF.5040104@tilera.com> (raw)
In-Reply-To: <20130111170043.D7CC39DC@kernel.stglabs.ibm.com>
On 1/11/2013 12:00 PM, Dave Hansen wrote:
> I'm looking for some Acked-bys on this from the various arch
> maintainers that it affects. I'd like to send it up to Linus
> in the next merge window. This is part of a larger series to
> clean up the "Kernel Hacking" menu:
>
> https://lkml.org/lkml/2012/12/17/306
>
> --
>
> 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.
>
Acked-by: Chris Metcalf <cmetcalf@tilera.com> [for tile]
--
Chris Metcalf, Tilera Corp.
http://www.tilera.com
next prev parent reply other threads:[~2013-01-11 17:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-11 17:00 [PATCH] consolidate per-arch stack overflow debugging options Dave Hansen
2013-01-11 17:10 ` James Hogan
2013-01-11 17:10 ` James Hogan
2013-01-11 17:36 ` Chris Metcalf [this message]
2013-01-11 17:36 ` Chris Metcalf
2013-01-12 1:00 ` Stephen Rothwell
2013-01-14 17:11 ` Dave Hansen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=50F04DAF.5040104@tilera.com \
--to=cmetcalf@tilera.com \
--cc=benh@kernel.crashing.org \
--cc=dave@linux.vnet.ibm.com \
--cc=dhowells@redhat.com \
--cc=hpa@zytor.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=paulus@samba.org \
--cc=ralf@linux-mips.org \
--cc=takata@linux-m32r.org \
--cc=tglx@linutronix.de \
--cc=uclinux-dist-devel@blackfin.uclinux.org \
--cc=vapier@gentoo.org \
--cc=x86@kernel.org \
--cc=yasutake.koichi@jp.panasonic.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.