From: michael.opdenacker@bootlin.com
To: docs@lists.yoctoproject.org
Cc: Michael Opdenacker <michael.opdenacker@bootlin.com>
Subject: [nanbield][PATCH 04/11] profile-manual: usage.rst: fix reference to bug report
Date: Mon, 25 Mar 2024 14:29:19 +0100 [thread overview]
Message-ID: <20240325132926.3018186-5-michael.opdenacker@bootlin.com> (raw)
In-Reply-To: <20240325132926.3018186-1-michael.opdenacker@bootlin.com>
From: Michael Opdenacker <michael.opdenacker@bootlin.com>
Allowing to remove nested parentheses in the text!
Signed-off-by: Michael Opdenacker <michael.opdenacker@bootlin.com>
---
documentation/profile-manual/usage.rst | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/documentation/profile-manual/usage.rst b/documentation/profile-manual/usage.rst
index 768349512a..0d368792b5 100644
--- a/documentation/profile-manual/usage.rst
+++ b/documentation/profile-manual/usage.rst
@@ -131,9 +131,9 @@ the summed counts at the end of the run::
59.836627620 seconds time elapsed
-Many times such a simple-minded test doesn't yield much of
-interest, but sometimes it does (see Real-world Yocto bug (slow
-loop-mounted write speed)).
+Such a simple-minded test doesn't always yield much of interest, but sometimes
+it does (see the :yocto_bugs:`Slow write speed on live images with denzil
+</show_bug.cgi?id=3049>` bug report).
Also, note that ``perf stat`` isn't restricted to a fixed set of counters
--- basically any event listed in the output of ``perf list`` can be tallied
--
2.34.1
next prev parent reply other threads:[~2024-03-25 13:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-25 13:29 [nanbield][PATCH 00/11] documentation backports michael.opdenacker
2024-03-25 13:29 ` [nanbield][PATCH 01/11] manuals: add initial stylechecks with Vale michael.opdenacker
2024-03-25 13:29 ` [nanbield][PATCH 02/11] profile-manual: usage.rst: formatting fixes michael.opdenacker
2024-03-25 13:29 ` [nanbield][PATCH 03/11] manuals: use "manual page(s)" michael.opdenacker
2024-03-25 13:29 ` michael.opdenacker [this message]
2024-03-25 13:29 ` [nanbield][PATCH 05/11] documentation: Makefile: remove releases.rst in "make clean" michael.opdenacker
2024-03-25 13:29 ` [nanbield][PATCH 06/11] migration-guides: add release notes for 4.0.17 michael.opdenacker
2024-03-25 13:29 ` [nanbield][PATCH 07/11] contributor-guide: be more specific about meta-* trees michael.opdenacker
2024-03-25 13:29 ` [nanbield][PATCH 08/11] profile-manual: usage.rst: further style improvements michael.opdenacker
2024-03-25 13:29 ` [nanbield][PATCH 09/11] ref-manual: add documentation of the variable SPDX_NAMESPACE_PREFIX michael.opdenacker
2024-03-25 13:29 ` [nanbield][PATCH 10/11] sdk-manual: correctly describe separate build-sysroots tasks in direct sdk workflows michael.opdenacker
2024-03-25 13:29 ` [nanbield][PATCH 11/11] dev-manual: improve descriptions of 'bitbake -S printdiff' michael.opdenacker
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=20240325132926.3018186-5-michael.opdenacker@bootlin.com \
--to=michael.opdenacker@bootlin.com \
--cc=docs@lists.yoctoproject.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.