[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAMuHMdXSNoXjxAbALr7O_dD_btJDGR58XaDa5=bd8NmL50wcaQ@mail.gmail.com>
Date: Tue, 2 Sep 2025 09:13:24 +0200
From: Geert Uytterhoeven <geert@...ux-m68k.org>
To: Harshit Mogalapalli <harshit.m.mogalapalli@...cle.com>
Cc: Rong Xu <xur@...gle.com>, Han Shen <shenhan@...gle.com>, Jonathan Corbet <corbet@....net>,
workflows@...r.kernel.org, linux-doc@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Documentation: dev-tools: Fix a typo in autofdo documentation
Hi Harshit,
On Mon, 1 Sept 2025 at 17:57, Harshit Mogalapalli
<harshit.m.mogalapalli@...cle.com> wrote:
> Use cat /proc/cpuinfo as opposed cat proc/cpuinfo.
>
> Signed-off-by: Harshit Mogalapalli <harshit.m.mogalapalli@...cle.com>
Thanks for your patch!
> --- 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::
>
One might say the path depends on where the proc filesystem is mounted ;-)
However, all other documentation (except for two occurrences in
Documentation/networking/proc_net_tcp.rst, which you may want to fix,
too) assumes /proc, so it is better to be consistent.
Reviewed-by: Geert Uytterhoeven <geert+renesas@...der.be>
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@...ux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
Powered by blists - more mailing lists