Hi Harshit, On Mon, 1 Sept 2025 at 17:57, Harshit Mogalapalli <harshit.m.mogalapalli@xxxxxxxxxx> wrote: > Use cat /proc/cpuinfo as opposed cat proc/cpuinfo. > > Signed-off-by: Harshit Mogalapalli <harshit.m.mogalapalli@xxxxxxxxxx> 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@xxxxxxxxx> Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@xxxxxxxxxxxxxx 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