From: Dave Hansen <dave@linux.vnet.ibm.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
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>,
Chris Metcalf <cmetcalf@tilera.com>,
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: Mon, 14 Jan 2013 09:11:58 -0800 [thread overview]
Message-ID: <50F43C5E.8030408@linux.vnet.ibm.com> (raw)
In-Reply-To: <20130112120053.3362ae67bf2d3b2cc6042aa4@canb.auug.org.au>
On 01/11/2013 05:00 PM, Stephen Rothwell wrote:
> On Fri, 11 Jan 2013 09:00:43 -0800 Dave Hansen <dave@linux.vnet.ibm.com> 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
>
> This should be added to linux-next soon, if possible. Either directly (if
> you have a tree I can fetch) or via some other maintainer's tree.
Hi Stephen,
I've got it stashed in here for the moment:
https://github.com/hansendc/linux/tree/kconfig-reorg
It was forked off 3.8-rc2.
prev parent reply other threads:[~2013-01-14 17:12 UTC|newest]
Thread overview: 5+ 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:36 ` Chris Metcalf
2013-01-12 1:00 ` Stephen Rothwell
2013-01-14 17:11 ` Dave Hansen [this message]
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=50F43C5E.8030408@linux.vnet.ibm.com \
--to=dave@linux.vnet.ibm.com \
--cc=benh@kernel.crashing.org \
--cc=cmetcalf@tilera.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=sfr@canb.auug.org.au \
--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 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).