From: James Clark <james.clark@linaro.org>
To: Ian Rogers <irogers@google.com>, Colin Ian King <colin.i.king@gmail.com>
Cc: kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org,
John Garry <john.garry@linux.dev>, Will Deacon <will@kernel.org>,
Mike Leach <mike.leach@arm.com>, Leo Yan <leo.yan@linux.dev>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Namhyung Kim <namhyung@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>,
Adrian Hunter <adrian.hunter@intel.com>,
linux-arm-kernel@lists.infradead.org, coresight@lists.linaro.org,
linux-perf-users@vger.kernel.org
Subject: Re: [PATCH][next] perf cs-etm: Fix spelling mistake "should't" -> "shouldn't"
Date: Tue, 3 Nov 2026 09:33:42 +0000 [thread overview]
Message-ID: <5d15b4aa-dfd6-4d01-86db-df748d84aa74@linaro.org> (raw)
In-Reply-To: <CAP-5=fVqUNoSQ72Hh5Zam3tyqooxpQ0+puAtTvr6omzmW3HZaQ@mail.gmail.com>
On 02/11/2026 18:01, Ian Rogers wrote:
> On Mon, Nov 2, 2026 at 2:52 AM James Clark <james.clark@linaro.org> wrote:
>>
>>
>>
>> On 28/10/2026 18:31, Colin Ian King wrote:
>>> There is a spelling mistake in a pr_err error message. Fix it.
>>>
>>> Signed-off-by: Colin Ian King <colin.i.king@gmail.com>
>>> ---
>>> tools/perf/util/cs-etm.c | 2 +-
>>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>>
>>> diff --git a/tools/perf/util/cs-etm.c b/tools/perf/util/cs-etm.c
>>> index bdcf94813129..65bce2450549 100644
>>> --- a/tools/perf/util/cs-etm.c
>>> +++ b/tools/perf/util/cs-etm.c
>>> @@ -434,7 +434,7 @@ static int cs_etm__map_unformatted_trace_ids(struct cs_etm_auxtrace *etm)
>>> continue;
>>>
>>> if (!intlist__empty(etmq->traceid_list)) {
>>> - pr_err("CS_ETM: Unformatted queue should't have trace ID\n");
>>> + pr_err("CS_ETM: Unformatted queue shouldn't have trace ID\n");
>>> return -EINVAL;
>>> }
>>>
>>
>> Reviewed-by: James Clark <james.clark@linaro.org>
>>
>
> I was curious how this passed Sashiko's review. Did Sashiko flag the
> spelling mistake but the fix was missed, or did Sashiko not flag it at
> all?
>
> Thanks!
> Ian
It reviewed it, but it didn't flag it. What kind of typos is it supposed
to look for? I haven't seen it flag one before.
I have a spellchecker in my IDE which didn't catch it either because
should is correct and t is only 1 letter. Maybe there is a setting I can
tweak.
next prev parent reply other threads:[~2026-11-03 9:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-28 18:31 Colin Ian King
2026-11-02 10:52 ` James Clark
2026-11-02 18:01 ` Ian Rogers
2026-11-03 9:33 ` James Clark [this message]
2026-11-03 17:07 ` Namhyung Kim
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=5d15b4aa-dfd6-4d01-86db-df748d84aa74@linaro.org \
--to=james.clark@linaro.org \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=colin.i.king@gmail.com \
--cc=coresight@lists.linaro.org \
--cc=irogers@google.com \
--cc=john.garry@linux.dev \
--cc=jolsa@kernel.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=leo.yan@linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mike.leach@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=suzuki.poulose@arm.com \
--cc=will@kernel.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
all inboxes | Powered by JetHome®