From: Mike Frysinger <vapier.adi@gmail.com>
To: Stephen Boyd <sboyd@codeaurora.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
uclinux-dist-devel@blackfin.uclinux.org,
linux-m32r@ml.linux-m32r.org, linux-mips@linux-mips.org,
linuxppc-dev@lists.ozlabs.org, linux-sh@vger.kernel.org,
sparclinux@vger.kernel.org, Chris Metcalf <cmetcalf@tilera.com>,
user-mode-linux-devel@lists.sourceforge.net, x86@kernel.org
Subject: Re: [PATCH] lib: Consolidate DEBUG_STACK_USAGE option
Date: Sat, 7 May 2011 09:57:36 -0400 [thread overview]
Message-ID: <BANLkTim4RFeFpj8uJsnm0gazLOMdYr8P1Q@mail.gmail.com> (raw)
In-Reply-To: <1304747831-2098-1-git-send-email-sboyd@codeaurora.org>
On Sat, May 7, 2011 at 01:57, Stephen Boyd wrote:
> Most arches define CONFIG_DEBUG_STACK_USAGE exactly the same way.
> Move it to lib/Kconfig.debug so each arch doesn't have to define
> it. This obviously makes the option generic, but that's fine
> because the config is already used in generic code.
>
> It's not obvious to me that sysrq-P actually does anything
> different with this option enabled, but I erred on the side of
> caution by keeping the most inclusive wording.
>
> Cc: uclinux-dist-devel@blackfin.uclinux.org
> arch/blackfin/Kconfig.debug | 9 ---------
Acked-by: Mike Frysinger <vapier@gentoo.org>
-mike
next prev parent reply other threads:[~2011-05-07 13:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-07 5:57 [PATCH] lib: Consolidate DEBUG_STACK_USAGE option Stephen Boyd
2011-05-07 5:57 ` Stephen Boyd
2011-05-07 7:58 ` David Miller
2011-05-07 9:34 ` richard -rw- weinberger
2011-05-07 9:34 ` richard -rw- weinberger
2011-05-07 13:57 ` Mike Frysinger [this message]
[not found] ` <1304747831-2098-1-git-send-email-sboyd-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2011-05-10 15:44 ` Ralf Baechle
2011-05-10 15:44 ` Ralf Baechle
2011-05-19 3:32 ` Benjamin Herrenschmidt
2011-05-19 3:32 ` Benjamin Herrenschmidt
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=BANLkTim4RFeFpj8uJsnm0gazLOMdYr8P1Q@mail.gmail.com \
--to=vapier.adi@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=cmetcalf@tilera.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m32r@ml.linux-m32r.org \
--cc=linux-mips@linux-mips.org \
--cc=linux-sh@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=sboyd@codeaurora.org \
--cc=sparclinux@vger.kernel.org \
--cc=uclinux-dist-devel@blackfin.uclinux.org \
--cc=user-mode-linux-devel@lists.sourceforge.net \
--cc=x86@kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).