linux-kernel - Re: [PATCH] perf script: Fix reference to perf insert instead of perf inject

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Tue, 9 Aug 2022 09:50:55 -0700
From:   Ian Rogers <irogers@...gle.com>
To:     Adrian Hunter <adrian.hunter@...el.com>
Cc:     Arnaldo Carvalho de Melo <acme@...nel.org>,
        Jiri Olsa <jolsa@...hat.com>,
        Namhyung Kim <namhyung@...nel.org>,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH] perf script: Fix reference to perf insert instead of perf inject

On Tue, Aug 9, 2022 at 5:33 AM Adrian Hunter <adrian.hunter@...el.com> wrote:
>
> Amend "perf insert" to "perf inject".
>
> Fixes: e28fb159f116 ("perf script: Add machine_pid and vcpu")
> Signed-off-by: Adrian Hunter <adrian.hunter@...el.com>

Acked-by: Ian Rogers <irogers@...gle.com>

Thanks,
Ian

> ---
>  tools/perf/Documentation/perf-script.txt | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/tools/perf/Documentation/perf-script.txt b/tools/perf/Documentation/perf-script.txt
> index c09cc44e50ee..4c95e79e2c39 100644
> --- a/tools/perf/Documentation/perf-script.txt
> +++ b/tools/perf/Documentation/perf-script.txt
> @@ -228,7 +228,7 @@ OPTIONS
>         Instruction Trace decoding.
>
>         The machine_pid and vcpu fields are derived from data resulting from using
> -       perf insert to insert a perf.data file recorded inside a virtual machine into
> +       perf inject to insert a perf.data file recorded inside a virtual machine into
>         a perf.data file recorded on the host at the same time.
>
>         Finally, a user may not set fields to none for all event types.
> --
> 2.25.1
>