From: Harshit Mogalapalli <harshit.m.mogalapalli@oracle.com>
To: Rong Xu <xur@google.com>, Han Shen <shenhan@google.com>,
Jonathan Corbet <corbet@lwn.net>,
workflows@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Documentation: dev-tools: Fix a typo in autofdo documentation
Date: Sun, 31 Aug 2025 20:42:48 +0530 [thread overview]
Message-ID: <1d3b87af-63c5-4d42-a981-87bc397bca60@oracle.com> (raw)
In-Reply-To: <20250831150710.1274546-1-harshit.m.mogalapalli@oracle.com>
Hi,
On 31/08/25 20:37, Harshit Mogalapalli wrote:
> Use cat /proc/cpuinfo as opposed cat proc/cpuinfo.
>
Please ignore this, I had a typo in my commit message for a typo fix :(
Send a V2:
https://lore.kernel.org/all/20250831151118.1274826-1-harshit.m.mogalapalli@oracle.com/
Thanks,
Harshit> Signed-off-by: Harshit Mogalapalli
<harshit.m.mogalapalli@oracle.com>
> ---
> 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::
>
next prev parent reply other threads:[~2025-08-31 15:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-31 15:07 Harshit Mogalapalli
2025-08-31 15:12 ` Harshit Mogalapalli [this message]
2025-09-02 7:13 ` Geert Uytterhoeven
2025-09-02 13:02 ` Harshit Mogalapalli
2025-09-02 16:50 ` Rong Xu
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=1d3b87af-63c5-4d42-a981-87bc397bca60@oracle.com \
--to=harshit.m.mogalapalli@oracle.com \
--cc=corbet@lwn.net \
--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