From: Charlie Jenkins <charlie@rivosinc.com>
To: I Hsin Cheng <richard120310@gmail.com>
Cc: corbet@lwn.net, acme@redhat.com, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, skhan@linuxfoundation.org
Subject: Re: [PATCH] docs: Correct installation instruction
Date: Wed, 5 Mar 2025 19:13:43 -0800 [thread overview]
Message-ID: <Z8kS5yd4znhULlSY@ghost> (raw)
In-Reply-To: <20250306030708.8133-1-richard120310@gmail.com>
On Thu, Mar 06, 2025 at 11:07:08AM +0800, I Hsin Cheng wrote:
> Ammend missing "install" operation keyword after "apt-get", and fix
> "build-essentials" to "build-essential".
>
> Signed-off-by: I Hsin Cheng <richard120310@gmail.com>
Reviewed-by: Charlie Jenkins <charlie@rivosinc.com>
> ---
> Documentation/admin-guide/workload-tracing.rst | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/admin-guide/workload-tracing.rst b/Documentation/admin-guide/workload-tracing.rst
> index 6be38c1b9c5b..d6313890ee41 100644
> --- a/Documentation/admin-guide/workload-tracing.rst
> +++ b/Documentation/admin-guide/workload-tracing.rst
> @@ -82,7 +82,7 @@ Install tools to build Linux kernel and tools in kernel repository.
> scripts/ver_linux is a good way to check if your system already has
> the necessary tools::
>
> - sudo apt-get build-essentials flex bison yacc
> + sudo apt-get install build-essential flex bison yacc
> sudo apt install libelf-dev systemtap-sdt-dev libslang2-dev libperl-dev libdw-dev
>
> cscope is a good tool to browse kernel sources. Let's install it now::
> --
> 2.43.0
>
next prev parent reply other threads:[~2025-03-06 3:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-06 3:07 [PATCH] docs: Correct installation instruction I Hsin Cheng
2025-03-06 3:13 ` Charlie Jenkins [this message]
2025-03-12 22:40 ` Jonathan Corbet
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=Z8kS5yd4znhULlSY@ghost \
--to=charlie@rivosinc.com \
--cc=acme@redhat.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=richard120310@gmail.com \
--cc=skhan@linuxfoundation.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).