All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: David Howells <dhowells@redhat.com>
Cc: uclinux-dev@uclinux.org, David McCullough <davidm@snapgear.com>,
	Greg Ungerer <gerg@uclinux.org>, Paul Mundt <lethal@linux-sh.org>,
	linux-kernel@vger.kernel.org,
	uclinux-dist-devel@blackfin.uclinux.org
Subject: Re: [PATCH v2] NOMMU: add [stack] label to per-process maps output
Date: Mon, 24 May 2010 01:35:12 -0400	[thread overview]
Message-ID: <201005240135.14259.vapier@gentoo.org> (raw)
In-Reply-To: <19310.1261497490@redhat.com>

[-- Attachment #1: Type: Text/Plain, Size: 554 bytes --]

On Tuesday 22 December 2009 10:58:10 David Howells wrote:
> Okay.  I've adjusted the desciption of the patch a little (see attached).
> 
> David
> ---
> From: Mike Frysinger <vapier@gentoo.org>
> Subject: [PATCH] NOMMU: Add '[stack]' label to /proc/pid/maps output
> 
> Add support to the NOMMU /proc/pid/maps file to show which mapping is the
> stack of the original thread after execve.  This is largely based on the
> MMU code. Subsidiary thread stacks are not indicated.

was there something holding this back from being merged ?
-mike

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

      reply	other threads:[~2010-05-24  5:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-15 23:55 [PATCH] NOMMU: add [stack] label to per-process maps output Mike Frysinger
2009-12-16  8:54 ` David Howells
2009-12-16 16:59 ` David Howells
2009-12-16 19:36   ` [uClinux-dev] " Mike Frysinger
2009-12-17 22:49   ` Mike Frysinger
2009-12-17 23:27     ` David Howells
2009-12-21 14:35   ` [PATCH v2] " Mike Frysinger
2009-12-22 15:58     ` David Howells
2010-05-24  5:35       ` Mike Frysinger [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=201005240135.14259.vapier@gentoo.org \
    --to=vapier@gentoo.org \
    --cc=davidm@snapgear.com \
    --cc=dhowells@redhat.com \
    --cc=gerg@uclinux.org \
    --cc=lethal@linux-sh.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=uclinux-dev@uclinux.org \
    --cc=uclinux-dist-devel@blackfin.uclinux.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 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.