From: Adrian Hunter <adrian.hunter@intel.com>
To: Andi Kleen <ak@linux.intel.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Jiri Olsa <jolsa@redhat.com>, linux-kernel@vger.kernel.org
Subject: [PATCH 3/3] perf intel-pt: Update intel-pt.txt file with new location of the documentation
Date: Wed, 11 Mar 2020 14:20:34 +0200 [thread overview]
Message-ID: <20200311122034.3697-4-adrian.hunter@intel.com> (raw)
In-Reply-To: <20200311122034.3697-1-adrian.hunter@intel.com>
Make it easy for people looking in intel-pt.txt to find the new file.
Signed-off-by: Adrian Hunter <adrian.hunter@intel.com>
---
tools/perf/Documentation/intel-pt.txt | 1 +
1 file changed, 1 insertion(+)
create mode 100644 tools/perf/Documentation/intel-pt.txt
diff --git a/tools/perf/Documentation/intel-pt.txt b/tools/perf/Documentation/intel-pt.txt
new file mode 100644
index 000000000000..fd9241a1b987
--- /dev/null
+++ b/tools/perf/Documentation/intel-pt.txt
@@ -0,0 +1 @@
+Documentation for support for Intel Processor Trace within perf tools' has moved to file perf-intel-pt.txt
--
2.17.1
next prev parent reply other threads:[~2020-03-11 12:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-11 12:20 [PATCH 0/3] perf intel-pt: Intel PT man page Adrian Hunter
2020-03-11 12:20 ` [PATCH 1/3] perf intel-pt: Rename intel-pt.txt and put it in man page format Adrian Hunter
2020-03-19 14:10 ` [tip: perf/core] " tip-bot2 for Adrian Hunter
2020-03-11 12:20 ` [PATCH 2/3] perf intel-pt: Add Intel PT man page references Adrian Hunter
2020-03-19 14:10 ` [tip: perf/core] " tip-bot2 for Adrian Hunter
2020-03-11 12:20 ` Adrian Hunter [this message]
2020-03-11 14:03 ` [PATCH 3/3] perf intel-pt: Update intel-pt.txt file with new location of the documentation Arnaldo Carvalho de Melo
2020-03-13 10:04 ` Adrian Hunter
2020-03-19 14:10 ` [tip: perf/core] " tip-bot2 for Adrian Hunter
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=20200311122034.3697-4-adrian.hunter@intel.com \
--to=adrian.hunter@intel.com \
--cc=acme@kernel.org \
--cc=ak@linux.intel.com \
--cc=jolsa@redhat.com \
--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 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.