linux-trace-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Tzvetomir Stoyanov (VMware)" <tz.stoyanov@gmail.com>
To: rostedt@goodmis.org, y.karadz@gmail.com
Cc: linux-trace-devel@vger.kernel.org
Subject: [PATCH v7 12/15] libtracefs: Do not clean sqlhist man page source
Date: Mon, 15 Nov 2021 12:45:53 +0200	[thread overview]
Message-ID: <20211115104556.121359-13-tz.stoyanov@gmail.com> (raw)
In-Reply-To: <20211115104556.121359-1-tz.stoyanov@gmail.com>

The "make doc_clean" command assumes that all *.1 files are being
generated with "make doc" command and removes all of them. This
assumption is wrong, as the sources of man pages from section one
have prefix "*.txt.1" and must not be removed. A more precise filtering
is added, so only files generated during "make doc" are removed.

Signed-off-by: Tzvetomir Stoyanov (VMware) <tz.stoyanov@gmail.com>
---
 Documentation/Makefile | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/Documentation/Makefile b/Documentation/Makefile
index 0c00505..92a67aa 100644
--- a/Documentation/Makefile
+++ b/Documentation/Makefile
@@ -197,7 +197,8 @@ endif
 CLEAN_FILES =					\
 	$(MAN_XML) $(addsuffix +,$(MAN_XML))	\
 	$(MAN_HTML) $(addsuffix +,$(MAN_HTML))	\
-	$(DOC_MAN3) *.3 *.1 *.m
+	$(filter-out $(MAN1_TEXT),$(wildcard *.1)) \
+	$(DOC_MAN3) *.3 *.m
 
 clean:
 	$(Q) $(RM) $(CLEAN_FILES)
-- 
2.33.1


  parent reply	other threads:[~2021-11-15 10:46 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-15 10:45 [PATCH v7 00/15] libtracefs dynamic events support Tzvetomir Stoyanov (VMware)
2021-11-15 10:45 ` [PATCH v7 01/15] libtracefs: New APIs for dynamic events Tzvetomir Stoyanov (VMware)
2021-11-15 10:45 ` [PATCH v7 02/15] libtracefs: New APIs for kprobe allocation Tzvetomir Stoyanov (VMware)
2021-11-15 10:45 ` [PATCH v7 03/15] libtracefs: Remove redundant kprobes APIs Tzvetomir Stoyanov (VMware)
2021-11-15 10:45 ` [PATCH v7 04/15] libtracefs: Reimplement kprobe raw APIs Tzvetomir Stoyanov (VMware)
2021-11-15 10:45 ` [PATCH v7 05/15] libtracefs: Extend kprobes unit test Tzvetomir Stoyanov (VMware)
2021-11-15 10:45 ` [PATCH v7 06/15] libtracefs: Rename tracefs_synth_init API Tzvetomir Stoyanov (VMware)
2021-11-15 10:45 ` [PATCH v7 07/15] libtracefs: Use the internal dynamic events API when creating synthetic events Tzvetomir Stoyanov (VMware)
2021-11-15 10:45 ` [PATCH v7 08/15] libtracefs: Remove instance parameter from synthetic events APIs Tzvetomir Stoyanov (VMware)
2021-11-15 10:45 ` [PATCH v7 09/15] libtracefs: Add unit test for synthetic events Tzvetomir Stoyanov (VMware)
2021-11-15 10:45 ` [PATCH v7 10/15] libtracefs: Update kprobes man pages Tzvetomir Stoyanov (VMware)
2021-11-15 10:45 ` [PATCH v7 11/15] libtracefs: Document dynamic events APIs Tzvetomir Stoyanov (VMware)
2021-11-15 10:45 ` Tzvetomir Stoyanov (VMware) [this message]
2021-11-15 10:45 ` [PATCH v7 13/15] libtracefs: Introduce eprobe API Tzvetomir Stoyanov (VMware)
2021-11-15 10:45 ` [PATCH v7 14/15] libtracefs: Add utest for event probes Tzvetomir Stoyanov (VMware)
2021-11-15 10:45 ` [PATCH v7 15/15] libtracefs: Document eprobe API Tzvetomir Stoyanov (VMware)

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=20211115104556.121359-13-tz.stoyanov@gmail.com \
    --to=tz.stoyanov@gmail.com \
    --cc=linux-trace-devel@vger.kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=y.karadz@gmail.com \
    /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).