All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: build warning after merge of the ftrace tree
Date: Mon, 23 Aug 2021 19:58:04 +1000	[thread overview]
Message-ID: <20210823195804.10c5758a@canb.auug.org.au> (raw)

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

Hi all,

After merging the ftrace tree, today's linux-next build (htmldocs)
produced this warning:

Documentation/trace/histogram.rst:80: WARNING: Malformed table.
Text in column margin in table line 8.

=========== ==========================================
.hex        display a number as a hex value
.sym        display an address as a symbol
.sym-offset display an address as a symbol and offset
.syscall    display a syscall id as a system call name
.execname   display a common_pid as a program name
.log2       display log2 value rather than raw number
.buckets=size  display grouping of values rather than raw number
.usecs      display a common_timestamp in microseconds
=========== ==========================================

Introduced by commit

  370364351926 ("tracing/histogram: Update the documentation for the buckets modifier")

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

             reply	other threads:[~2021-08-23  9:58 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-23  9:58 Stephen Rothwell [this message]
2021-08-23 14:00 ` linux-next: build warning after merge of the ftrace tree Steven Rostedt
2021-08-24 10:53   ` Stephen Rothwell
  -- strict thread matches above, loose matches on Subject: below --
2024-05-15  2:48 Stephen Rothwell
2024-05-15  4:49 ` Steven Rostedt
2024-05-15  5:01   ` Steven Rostedt
2024-05-15  5:11 ` Stephen Rothwell
2024-05-15  5:13   ` Stephen Rothwell
2023-06-23  4:35 Stephen Rothwell
2023-06-23  6:53 ` Donglin Peng
2022-11-25  3:10 Stephen Rothwell
2021-10-28 12:23 Stephen Rothwell
2021-10-28 13:16 ` Steven Rostedt
2021-10-28 21:10   ` Stephen Rothwell
2021-10-28 21:29     ` Kalesh Singh
2021-10-28 22:36       ` Stephen Rothwell
2021-10-28 21:30     ` Steven Rostedt
2021-10-25 23:35 Stephen Rothwell
2021-10-26 12:15 ` Masami Hiramatsu
2021-10-25  4:39 Stephen Rothwell
2021-10-25  6:13 ` Masami Hiramatsu
2020-11-16  6:35 Stephen Rothwell
2020-11-16 17:43 ` Steven Rostedt
2020-11-16 19:24   ` Jonathan Corbet
2020-11-16 20:25     ` Steven Rostedt
2020-11-16 20:29       ` Jonathan Corbet
2020-11-16 20:35         ` Steven Rostedt
2020-08-05  4:21 Stephen Rothwell
2019-11-15  3:02 Stephen Rothwell
2019-11-15  3:43 ` Steven Rostedt
2014-06-04  6:09 Stephen Rothwell
2014-06-04 16:26 ` Steven Rostedt
2014-06-04 16:49   ` Stephen Rothwell
2014-06-05  0:20   ` Fengguang Wu
2014-06-05  1:00     ` Steven Rostedt
2014-06-05  1:03       ` Fengguang Wu
2014-06-05  1:12         ` Steven Rostedt
2014-06-05  1:20           ` Steven Rostedt
2014-06-05  1:33           ` Fengguang Wu
2014-06-05  1:39             ` Steven Rostedt
2014-06-05  2:14               ` Fengguang Wu
2014-06-05  2:36                 ` Steven Rostedt
2014-06-05  2:50                   ` Fengguang Wu
2014-06-05  3:03                   ` Fengguang Wu
2014-06-05  3:13                     ` Steven Rostedt
2014-06-05  3:42                       ` Fengguang Wu
2014-06-05  2:38                 ` Steven Rostedt
2014-06-05  2:44                   ` Fengguang Wu
2014-06-05  2:46                 ` 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=20210823195804.10c5758a@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=rostedt@goodmis.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.