From: Jonathan Corbet <corbet@lwn.net>
To: Harshit Mogalapalli <harshit.m.mogalapalli@oracle.com>,
Rong Xu <xur@google.com>, Han Shen <shenhan@google.com>,
workflows@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: Harshit Mogalapalli <harshit.m.mogalapalli@oracle.com>
Subject: Re: [PATCH v2] Documentation: dev-tools: Fix a typo in autofdo documentation
Date: Wed, 03 Sep 2025 15:45:23 -0600 [thread overview]
Message-ID: <87seh3p5vw.fsf@trenco.lwn.net> (raw)
In-Reply-To: <20250831151118.1274826-1-harshit.m.mogalapalli@oracle.com>
Harshit Mogalapalli <harshit.m.mogalapalli@oracle.com> writes:
> Use "cat /proc/cpuinfo" instead of "cat proc/cpuinfo".
>
> Signed-off-by: Harshit Mogalapalli <harshit.m.mogalapalli@oracle.com>
> ---
> v1 -> v2: Fix a typo in commit message.
>
> Documentation/dev-tools/autofdo.rst | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/dev-tools/autofdo.rst b/Documentation/dev-tools/autofdo.rst
> index 1f0a451e9ccd..bcf06e7d6ffa 100644
> --- a/Documentation/dev-tools/autofdo.rst
> +++ b/Documentation/dev-tools/autofdo.rst
> @@ -131,11 +131,11 @@ Here is an example workflow for AutoFDO kernel:
>
> For Zen3::
>
> - $ cat proc/cpuinfo | grep " brs"
> + $ cat /proc/cpuinfo | grep " brs"
>
> For Zen4::
>
> - $ cat proc/cpuinfo | grep amd_lbr_v2
> + $ cat /proc/cpuinfo | grep amd_lbr_v2
>
> The following command generated the perf data file::
Applied, thanks.
jon
prev parent reply other threads:[~2025-09-03 21:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-31 15:11 Harshit Mogalapalli
2025-09-03 21:45 ` Jonathan Corbet [this message]
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=87seh3p5vw.fsf@trenco.lwn.net \
--to=corbet@lwn.net \
--cc=harshit.m.mogalapalli@oracle.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shenhan@google.com \
--cc=workflows@vger.kernel.org \
--cc=xur@google.com \
/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