public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ben Hutchings <benh@debian.org>
To: Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@redhat.com>,
	Arnaldo Carvalho de Melo <acme@kernel.org>,
	Namhyung Kim <namhyung@kernel.org>
Cc: linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/2] perf docs: Fix build with asciidoctor
Date: Sun, 23 Mar 2025 21:36:33 +0100	[thread overview]
Message-ID: <Z-Bw0XbCBfn7yrcs@decadent.org.uk> (raw)

[-- Attachment #1: Type: text/plain, Size: 833 bytes --]

Although I made a minor fix in 2023 for asciidoctor builds, I missed
an earlier regression from 2020 that had been fixed locally in the
Debian package but not upstream.  I'm sending 2 more fixes that should
make all manual pages build properly with asciidoctor.

However, given that asciidoctor support has been broken upstream for
nearly 5 years now, it might make more sense to remove it instead.  We
only moved to asciidoctor in Debian to remove a Python 2 dependency.
Since asciidoc was ported to Python 3 that's no longer a concern.

Ben.

Ben Hutchings (2):
  perf docs: Fix build with asciidoctor
  perf docs: Fix perf-check manual page built with asciidoctor

 tools/perf/Documentation/Makefile       | 17 +++++++++--------
 tools/perf/Documentation/perf-check.txt |  2 +-
 2 files changed, 10 insertions(+), 9 deletions(-)


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

             reply	other threads:[~2025-03-23 20:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-23 20:36 Ben Hutchings [this message]
2025-03-23 20:37 ` [PATCH 1/2] perf docs: Fix build with asciidoctor Ben Hutchings
2025-03-23 20:37 ` [PATCH 2/2] perf docs: Fix perf-check manual page built " Ben Hutchings

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=Z-Bw0XbCBfn7yrcs@decadent.org.uk \
    --to=benh@debian.org \
    --cc=acme@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --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