From: Arjan van de Ven <arjan@infradead.org>
To: Albert Cahalan <acahalan@gmail.com>
Cc: linux-kernel@vger.kernel.org, akpm@osdl.org
Subject: Re: [PATCH] add /proc/*/pmap files
Date: Sun, 22 Jan 2006 11:03:12 +0100 [thread overview]
Message-ID: <1137924193.3328.8.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <787b0d920601220150n2e34e376i856cc583a372e1f2@mail.gmail.com>
>
> This applies to -git4, grabbed Saturday night.
with this much wrapping... no it doesn't ;-)
next prev parent reply other threads:[~2006-01-22 10:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-22 9:50 [PATCH] add /proc/*/pmap files Albert Cahalan
2006-01-22 10:03 ` Arjan van de Ven [this message]
2006-01-22 10:38 ` Kyle Moffett
2006-01-22 10:39 ` Willy Tarreau
2006-01-22 14:32 ` Jan Engelhardt
2006-01-22 20:02 ` Albert Cahalan
2006-01-22 14:36 ` Arjan van de Ven
2006-01-22 19:17 ` Albert Cahalan
2006-01-22 19:44 ` Arjan van de Ven
2006-01-22 19:58 ` Andrew Morton
2006-01-22 20:40 ` Albert Cahalan
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=1137924193.3328.8.camel@laptopd505.fenrus.org \
--to=arjan@infradead.org \
--cc=acahalan@gmail.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.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).