From: Steven Rostedt <rostedt@goodmis.org>
To: Roland Hieber <rhi@pengutronix.de>
Cc: Jonathan Corbet <corbet@lwn.net>, Ingo Molnar <mingo@redhat.com>,
Daniel Bristot de Oliveira <bristot@kernel.org>,
linux-doc@vger.kernel.org
Subject: Re: [PATCH 2/3] docs: trace: bring headings in order
Date: Sun, 13 Mar 2022 20:01:43 -0400 [thread overview]
Message-ID: <20220313200143.3328cb87@rorschach.local.home> (raw)
In-Reply-To: <20220313105557.172732-2-rhi@pengutronix.de>
On Sun, 13 Mar 2022 11:55:56 +0100
Roland Hieber <rhi@pengutronix.de> wrote:
>
> -2.2 Inter-event hist triggers
> ------------------------------
> +Inter-event hist triggers
> +-------------------------
>
> Inter-event hist triggers are hist triggers that combine values from
> one or more other events and create a histogram using that data. Data
> @@ -1676,8 +1676,8 @@ pseudo-file.
>
> These features are described in more detail in the following sections.
>
> -2.2.1 Histogram Variables
> --------------------------
> +Histogram Variables
> +-------------------
>
Histogram Variables is a sub section of Inter-event hist triggers,
which this now removes. This affects the output a breaks the intention
of the document. I haven't looked at all the other updates, I just
stopped when I saw this.
-- Steve
next prev parent reply other threads:[~2022-03-14 0:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-13 10:55 [PATCH 1/3] docs: tracing: use refs for cross-referencing Roland Hieber
2022-03-13 10:55 ` [PATCH 2/3] docs: trace: bring headings in order Roland Hieber
2022-03-14 0:01 ` Steven Rostedt [this message]
2022-03-14 11:28 ` Roland Hieber
2022-03-13 10:55 ` [PATCH 3/3] docs: trace: events: apply literal markup Roland Hieber
2022-03-14 0:04 ` Steven Rostedt
2022-03-13 23:55 ` [PATCH 1/3] docs: tracing: use refs for cross-referencing Steven Rostedt
2022-03-14 11:46 ` Roland Hieber
2022-03-16 21:48 ` Jonathan Corbet
2022-03-16 21:52 ` Steven Rostedt
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=20220313200143.3328cb87@rorschach.local.home \
--to=rostedt@goodmis.org \
--cc=bristot@kernel.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rhi@pengutronix.de \
/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).