From: Ian Rogers <irogers@google.com>
To: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@redhat.com>, Namhyung Kim <namhyung@kernel.org>,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: eranian@google.com, Ian Rogers <irogers@google.com>
Subject: [PATCH 7/7] perf doc: Reorganize ARTICLES variables.
Date: Wed, 14 Jul 2021 18:33:43 -0700 [thread overview]
Message-ID: <20210715013343.2286699-8-irogers@google.com> (raw)
In-Reply-To: <20210715013343.2286699-1-irogers@google.com>
Place early, as they are in the git Makefile. Remove references to a
'technical` directory that doesn't exist in perf.
Signed-off-by: Ian Rogers <irogers@google.com>
---
tools/perf/Documentation/Makefile | 11 ++++-------
1 file changed, 4 insertions(+), 7 deletions(-)
diff --git a/tools/perf/Documentation/Makefile b/tools/perf/Documentation/Makefile
index 9d991b14ac4b..6e7b88917ca0 100644
--- a/tools/perf/Documentation/Makefile
+++ b/tools/perf/Documentation/Makefile
@@ -2,6 +2,10 @@
include ../../scripts/Makefile.include
include ../../scripts/utilities.mak
+ARTICLES =
+# with their own formatting rules.
+SP_ARTICLES =
+
MAN1_TXT= \
$(filter-out $(addsuffix .txt, $(ARTICLES) $(SP_ARTICLES)), \
$(wildcard perf-*.txt)) \
@@ -16,13 +20,6 @@ _MAN_HTML=$(patsubst %.txt,%.html,$(MAN_TXT))
MAN_XML=$(addprefix $(OUTPUT),$(_MAN_XML))
MAN_HTML=$(addprefix $(OUTPUT),$(_MAN_HTML))
-ARTICLES =
-# with their own formatting rules.
-SP_ARTICLES =
-API_DOCS = $(patsubst %.txt,%,$(filter-out technical/api-index-skel.txt technical/api-index.txt, $(wildcard technical/api-*.txt)))
-SP_ARTICLES += $(API_DOCS)
-SP_ARTICLES += technical/api-index
-
_DOC_HTML = $(_MAN_HTML)
_DOC_HTML+=$(patsubst %,%.html,$(ARTICLES) $(SP_ARTICLES))
DOC_HTML=$(addprefix $(OUTPUT),$(_DOC_HTML))
--
2.32.0.402.g57bb445576-goog
next prev parent reply other threads:[~2021-07-15 1:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-15 1:33 [PATCH 0/7] Tidy perf Documentation build Ian Rogers
2021-07-15 1:33 ` [PATCH 1/7] perf doc: Fix perfman.info build Ian Rogers
2021-07-15 1:33 ` [PATCH 2/7] perf doc: Fix doc.dep Ian Rogers
2021-07-15 1:33 ` [PATCH 3/7] perf doc: Remove references to user-manual Ian Rogers
2021-07-15 1:33 ` [PATCH 4/7] perf doc: Add info pages to all target Ian Rogers
2021-07-23 18:27 ` Arnaldo Carvalho de Melo
2021-07-23 18:53 ` Arnaldo Carvalho de Melo
2021-07-23 18:56 ` Arnaldo Carvalho de Melo
2021-07-23 21:03 ` Ian Rogers
2021-07-23 22:28 ` Arnaldo
2021-07-15 1:33 ` [PATCH 5/7] perf doc: Remove cmd-list.perl references Ian Rogers
2021-07-15 1:33 ` [PATCH 6/7] perf doc: Remove howto-index.sh related references Ian Rogers
2021-07-15 1:33 ` Ian Rogers [this message]
2021-07-19 19:32 ` [PATCH 0/7] Tidy perf Documentation build Namhyung Kim
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=20210715013343.2286699-8-irogers@google.com \
--to=irogers@google.com \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=eranian@google.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.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).