From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Johannes Erdfelt <johannes@erdfelt.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>, linus@goop.org
Subject: Re: [PATCH] address-space identification for /proc
Date: Thu, 26 Oct 2000 18:21:37 -0700 [thread overview]
Message-ID: <20001026182137.A31159@goop.org> (raw)
In-Reply-To: <20001026154527.A30463@goop.org> <20001026155225.B30463@goop.org> <20001026190126.E28472@sventech.com>
In-Reply-To: <20001026190126.E28472@sventech.com>; from johannes@erdfelt.com on Thu, Oct 26, 2000 at 07:01:26PM -0400
[-- Attachment #1: Type: text/plain, Size: 310 bytes --]
On Thu, Oct 26, 2000 at 07:01:26PM -0400, Johannes Erdfelt wrote:
> and even more obvious:
>
> + buffer += sprintf(buffer, "ASID:\t%p\n", mm);
>
> Actually putting it into the buffer would be useful as well :)
That serves me right for hand-editing patches.
J
--
Repeat to self: I am not Linus
[-- Attachment #2: Type: application/pgp-signature, Size: 240 bytes --]
prev parent reply other threads:[~2000-10-27 1:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-26 22:45 [PATCH] address-space identification for /proc Jeremy Fitzhardinge
2000-10-26 22:52 ` Jeremy Fitzhardinge
2000-10-26 23:01 ` Johannes Erdfelt
2000-10-27 1:21 ` Jeremy Fitzhardinge [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=20001026182137.A31159@goop.org \
--to=jeremy@goop.org \
--cc=johannes@erdfelt.com \
--cc=linus@goop.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