Linux Documentation
 help / color / mirror / Atom feed
From: Cheng-Han Wu <hank20010209@gmail.com>
To: Jonathan Corbet <corbet@lwn.net>, Shuah Khan <skhan@linuxfoundation.org>
Cc: Randy Dunlap <rdunlap@infradead.org>,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	Cheng-Han Wu <hank20010209@gmail.com>
Subject: [PATCH 0/4] docs: admin-guide: improve workload tracing guide
Date: Sun,  3 May 2026 18:14:25 +0800	[thread overview]
Message-ID: <20260503101429.254394-1-hank20010209@gmail.com> (raw)

This series updates Documentation/admin-guide/workload-tracing.rst

  - Patch 1 fixes several typos.
  - Patch 2 fixes stress-ng and perf record command examples.
  - Patch 3 replaces a stale fixed "perf bench all" benchmark list with a
description of the command behavior and how to query available benchmarks.
  - Patch 4 mentions the kernel build system's cscope target and shows how 
to exclude directories with IGNORE_DIRS.

Built test with:
  make SPHINXDIRS=admin-guide htmldocs

Cheng-Han Wu (4):
  docs: admin-guide: fix typos in workload tracing guide
  docs: admin-guide: fix stress-ng command examples
  docs: admin-guide: clarify perf bench all behavior
  docs: admin-guide: add IGNORE_DIRS example for cscope

 .../admin-guide/workload-tracing.rst          | 41 +++++++++++++------
 1 file changed, 29 insertions(+), 12 deletions(-)

-- 
2.52.0


             reply	other threads:[~2026-05-03 10:15 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-03 10:14 Cheng-Han Wu [this message]
2026-05-03 10:14 ` [PATCH 1/4] docs: admin-guide: fix typos in workload tracing guide Cheng-Han Wu
2026-05-05 18:26   ` Shuah Khan
2026-05-03 10:14 ` [PATCH 2/4] docs: admin-guide: fix stress-ng command examples Cheng-Han Wu
2026-05-05 18:27   ` Shuah Khan
2026-05-03 10:14 ` [PATCH 3/4] docs: admin-guide: clarify perf bench all behavior Cheng-Han Wu
2026-05-05 18:27   ` Shuah Khan
2026-05-03 10:14 ` [PATCH 4/4] docs: admin-guide: add IGNORE_DIRS example for cscope Cheng-Han Wu
2026-05-05 18:24   ` Shuah Khan

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=20260503101429.254394-1-hank20010209@gmail.com \
    --to=hank20010209@gmail.com \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@infradead.org \
    --cc=skhan@linuxfoundation.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