kernel-5.10/perf-xmlto-skip-validation.patch

diff --git a/tools/perf/Documentation/Makefile b/tools/perf/Documentation/Makefile
index 3ba1c0b..2f5070f 100644
--- a/tools/perf/Documentation/Makefile
+++ b/tools/perf/Documentation/Makefile
@@ -49,7 +49,7 @@ man7dir=$(mandir)/man7
 ASCIIDOC=asciidoc
 ASCIIDOC_EXTRA = --unsafe
 MANPAGE_XSL = manpage-normal.xsl
-XMLTO_EXTRA =
+XMLTO_EXTRA = --skip-validation
 INSTALL?=install
 RM ?= rm -f
 DOC_REF = origin/man
Keep the patches in the kernel project instead of a separate one Earlier, the patches were kept in the respective branches of a separate project, https://abf.io/soft/kernel-patches-and-configs. And before that - in the custom tarballs. Now all the patches are kept here along with the spec file and are applied the default way rather than by separate scripts. This should make the maintenance of the patches as well as the experiments with the new ones a lot easier. The previous scheme seemed to offer a bit more flexibility (different patch sets for different cases) at the cost of maintenance. But as it turned out, that flexibility was not worth it and was rarely used, at most. 2016-07-26 11:24:24 +03:00			`diff --git a/tools/perf/Documentation/Makefile b/tools/perf/Documentation/Makefile`
			`index 3ba1c0b..2f5070f 100644`
			`--- a/tools/perf/Documentation/Makefile`
			`+++ b/tools/perf/Documentation/Makefile`
			`@@ -49,7 +49,7 @@ man7dir=$(mandir)/man7`
			`ASCIIDOC=asciidoc`
			`ASCIIDOC_EXTRA = --unsafe`
			`MANPAGE_XSL = manpage-normal.xsl`
			`-XMLTO_EXTRA =`
			`+XMLTO_EXTRA = --skip-validation`
			`INSTALL?=install`
			`RM ?= rm -f`
			`DOC_REF = origin/man`