From: Leo Yan <leo.yan@linaro.org>
To: Will Deacon <will@kernel.org>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@redhat.com>, Namhyung Kim <namhyung@kernel.org>,
Florian Fainelli <f.fainelli@gmail.com>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] perf tests: Fix a typo
Date: Wed, 23 Oct 2019 17:28:33 +0800 [thread overview]
Message-ID: <20191023092833.GE32731@leoy-ThinkPad-X240s> (raw)
In-Reply-To: <20191023091416.GB25798@willie-the-truck>
On Wed, Oct 23, 2019 at 10:14:17AM +0100, Will Deacon wrote:
> On Wed, Oct 23, 2019 at 04:33:24PM +0800, Leo Yan wrote:
> > Correct typo in comment: s/suck/stuck.
> >
> > Signed-off-by: Leo Yan <leo.yan@linaro.org>
> > ---
> > tools/perf/tests/bp_signal.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/tools/perf/tests/bp_signal.c b/tools/perf/tests/bp_signal.c
> > index 166f411568a5..415903b48578 100644
> > --- a/tools/perf/tests/bp_signal.c
> > +++ b/tools/perf/tests/bp_signal.c
> > @@ -295,7 +295,7 @@ bool test__bp_signal_is_supported(void)
> > * breakpointed instruction.
> > *
> > * Since arm64 has the same issue with arm for the single-step
> > - * handling, this case also gets suck on the breakpointed
> > + * handling, this case also gets stuck on the breakpointed
> > * instruction.
> > *
> > * Just disable the test for these architectures until these
>
> Thanks, and sorry for only spotting this after the offending patch was
> merged.
No worries and thanks for review.
next prev parent reply other threads:[~2019-10-23 9:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-23 8:33 Leo Yan
2019-10-23 9:14 ` Will Deacon
2019-10-23 9:28 ` Leo Yan [this message]
2019-11-12 11:18 ` [tip: perf/core] " tip-bot2 for Leo Yan
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=20191023092833.GE32731@leoy-ThinkPad-X240s \
--to=leo.yan@linaro.org \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=f.fainelli@gmail.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--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®