public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Mi, Dapeng" <dapeng1.mi@linux.intel.com>
To: Ian Rogers <irogers@google.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@redhat.com>,
	Arnaldo Carvalho de Melo <acme@kernel.org>,
	Namhyung Kim <namhyung@kernel.org>,
	Adrian Hunter <adrian.hunter@intel.com>,
	Alexander Shishkin <alexander.shishkin@linux.intel.com>,
	Kan Liang <kan.liang@linux.intel.com>,
	linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org,
	Dapeng Mi <dapeng1.mi@intel.com>
Subject: Re: [PATCH] perf tools: Fix incorrect --user-regs comments
Date: Thu, 3 Apr 2025 08:42:16 +0800	[thread overview]
Message-ID: <762e01c1-c78c-4bd7-aec4-4cc56563da20@linux.intel.com> (raw)
In-Reply-To: <CAP-5=fU3Tam3PXd94ibVQZU=Kk4Q_=z0i9o7kx-Vgm9qwK-mHA@mail.gmail.com>


On 4/3/2025 12:55 AM, Ian Rogers wrote:
> On Tue, Apr 1, 2025 at 8:58 PM Dapeng Mi <dapeng1.mi@linux.intel.com> wrote:
>> The comment of "--user-regs" option is not correct, fix it.
>>
>> "on interrupt," -> "on user space,"
> nit: I think "in user space" is more grammatical.

Sure.


>
>> Fixes: 84c417422798 ("perf record: Support direct --user-regs arguments")
>> Signed-off-by: Dapeng Mi <dapeng1.mi@linux.intel.com>
>> ---
>>  tools/perf/builtin-record.c | 2 +-
>>  1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/tools/perf/builtin-record.c b/tools/perf/builtin-record.c
>> index ba20bf7c011d..f21b133691d7 100644
>> --- a/tools/perf/builtin-record.c
>> +++ b/tools/perf/builtin-record.c
>> @@ -3480,7 +3480,7 @@ static struct option __record_options[] = {
>>                     "sample selected machine registers on interrupt,"
>>                     " use '-I?' to list register names", parse_intr_regs),
>>         OPT_CALLBACK_OPTARG(0, "user-regs", &record.opts.sample_user_regs, NULL, "any register",
>> -                   "sample selected machine registers on interrupt,"
>> +                   "sample selected machine registers on user space,"
> nit: "sample selected machine registers in user space"
>
> Reviewed-by: Ian Rogers <irogers@google.com>

Sure. Thanks for reviewing.


>
> Thanks,
> Ian
>
>>                     " use '--user-regs=?' to list register names", parse_user_regs),
>>         OPT_BOOLEAN(0, "running-time", &record.opts.running_time,
>>                     "Record running/enabled time of read (:S) events"),
>>
>> base-commit: 35d13f841a3d8159ef20d5e32a9ed3faa27875bc
>> --
>> 2.40.1
>>

      reply	other threads:[~2025-04-03  0:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-02  8:21 [PATCH] perf tools: Fix incorrect --user-regs comments Dapeng Mi
2025-04-02 16:55 ` Ian Rogers
2025-04-03  0:42   ` Mi, Dapeng [this message]

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=762e01c1-c78c-4bd7-aec4-4cc56563da20@linux.intel.com \
    --to=dapeng1.mi@linux.intel.com \
    --cc=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=dapeng1.mi@intel.com \
    --cc=irogers@google.com \
    --cc=kan.liang@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=namhyung@kernel.org \
    --cc=peterz@infradead.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