From: Randy Dunlap <randy.dunlap@oracle.com>
To: <eduard.munteanu@linux360.ro>
Cc: <fweisbec@gmail.com>, <mingo@elte.hu>,
<linux-kernel@vger.kernel.org>, <lizf@cn.fujitsu.com>,
<penberg@cs.helsinki.fi>
Subject: Re: [PATCH] Remove Documentation/trace/kmemtrace.txt
Date: Sun, 28 Mar 2010 09:09:17 -0700 (PDT) [thread overview]
Message-ID: <3fa4ae08-42db-4ee0-b86f-567997c35dd4@default> (raw)
Acked-by: Randy Dunlap <randy.dunlap@oracle.com>
Thanks.
---
~Randy
----- Original Message -----
From: eduard.munteanu@linux360.ro
To: mingo@elte.hu
Cc: randy.dunlap@oracle.com, lizf@cn.fujitsu.com, fweisbec@gmail.com, penberg@cs.helsinki.fi, linux-kernel@vger.kernel.org, eduard.munteanu@linux360.ro
Sent: Sunday, March 28, 2010 1:27:31 AM GMT -08:00 US/Canada Pacific
Subject: [PATCH] Remove Documentation/trace/kmemtrace.txt
The current implementation of kmemtrace has been based on ftrace for a
while. Documentation/trace/kmemtrace.txt concerns the old, relay-based
implementation, so it's outdated. This removes it to avoid confusion.
Signed-off-by: Eduard - Gabriel Munteanu <eduard.munteanu@linux360.ro>
---
Documentation/trace/kmemtrace.txt | 126 -------------------------------------
1 files changed, 0 insertions(+), 126 deletions(-)
delete mode 100644 Documentation/trace/kmemtrace.txt
next reply other threads:[~2010-03-28 16:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-28 16:09 Randy Dunlap [this message]
2010-03-28 18:56 ` [PATCH] Remove Documentation/trace/kmemtrace.txt Frederic Weisbecker
-- strict thread matches above, loose matches on Subject: below --
2010-03-27 4:27 kmemtrace.txt question: kernel parameter(s)? Randy Dunlap
2010-03-28 8:26 ` [PATCH] Remove Documentation/trace/kmemtrace.txt Eduard - Gabriel Munteanu
2010-03-28 8:33 ` Pekka Enberg
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=3fa4ae08-42db-4ee0-b86f-567997c35dd4@default \
--to=randy.dunlap@oracle.com \
--cc=eduard.munteanu@linux360.ro \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizf@cn.fujitsu.com \
--cc=mingo@elte.hu \
--cc=penberg@cs.helsinki.fi \
/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