linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Samuel Wu <wusamuel@google.com>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Samuel Wu <wusamuel@google.com>,
	kernel-team@android.com, linux-doc@vger.kernel.org,
	 linux-kernel@vger.kernel.org
Subject: [PATCH v1] Documentation/perf: Fix typo in dsu_pmu sysfs path
Date: Mon,  8 Dec 2025 11:46:19 -0800	[thread overview]
Message-ID: <20251208194619.1745453-1-wusamuel@google.com> (raw)

Correct a typo in the documented sysfs path for the ARM DynamIQ Shared
Unit (DSU) PMU. The `event_sources` directory name was singularized to
`event_source` to match the name defined in `kernel/events/core.c`.

Signed-off-by: Samuel Wu <wusamuel@google.com>
---
 Documentation/admin-guide/perf/arm_dsu_pmu.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Documentation/admin-guide/perf/arm_dsu_pmu.rst b/Documentation/admin-guide/perf/arm_dsu_pmu.rst
index 7fd34db75d13..ac43343d4882 100644
--- a/Documentation/admin-guide/perf/arm_dsu_pmu.rst
+++ b/Documentation/admin-guide/perf/arm_dsu_pmu.rst
@@ -16,7 +16,7 @@ registers. There is no way for the driver to determine if the other events
 are available or not. Hence the driver exposes only those events advertised
 by the DSU, in "events" directory under::
 
-  /sys/bus/event_sources/devices/arm_dsu_<N>/
+  /sys/bus/event_source/devices/arm_dsu_<N>/
 
 The user should refer to the TRM of the product to figure out the supported events
 and use the raw event code for the unlisted events.
-- 
2.52.0.223.gf5cc29aaa4-goog


                 reply	other threads:[~2025-12-08 19:46 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20251208194619.1745453-1-wusamuel@google.com \
    --to=wusamuel@google.com \
    --cc=corbet@lwn.net \
    --cc=kernel-team@android.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).