From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Namhyung Kim <namhyung@kernel.org>
Cc: Colin Ian King <colin.i.king@gmail.com>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>, Ian Rogers <irogers@google.com>,
Adrian Hunter <adrian.hunter@intel.com>,
linux-perf-users@vger.kernel.org,
kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH][next] perf/benchmark: Fix spelling mistake "synchronious" -> "synchronous"
Date: Mon, 4 Dec 2023 17:27:34 -0300 [thread overview]
Message-ID: <ZW42NiB4VK7Dp7oP@kernel.org> (raw)
In-Reply-To: <CAM9d7ch8GcZUXVEtPGh2QW8-_aiObq7ybU_7gY7LMcjRfOFvxw@mail.gmail.com>
Em Sat, Jul 01, 2023 at 10:57:33AM -0700, Namhyung Kim escreveu:
> Hello,
>
> On Fri, Jun 30, 2023 at 1:00 AM Colin Ian King <colin.i.king@gmail.com> wrote:
> >
> > There is a spelling mistake in an option description. Fix it.
> >
> > Signed-off-by: Colin Ian King <colin.i.king@gmail.com>
> > ---
> > tools/perf/bench/sched-seccomp-notify.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
>
> Hmm.. strange. I cannot see the bench/sched-seccomp-notify.c.
> Which tree are you based?
It went thru a different tree, but I got this while looking for
Acked-by patches and finally applied it.
- Arnaldo
> Thanks,
> Namhyung
>
>
> >
> > diff --git a/tools/perf/bench/sched-seccomp-notify.c b/tools/perf/bench/sched-seccomp-notify.c
> > index eac4ef60090f..2e8205c61141 100644
> > --- a/tools/perf/bench/sched-seccomp-notify.c
> > +++ b/tools/perf/bench/sched-seccomp-notify.c
> > @@ -33,7 +33,7 @@ static bool sync_mode;
> > static const struct option options[] = {
> > OPT_U64('l', "loop", &loops, "Specify number of loops"),
> > OPT_BOOLEAN('s', "sync-mode", &sync_mode,
> > - "Enable the synchronious mode for seccomp notifications"),
> > + "Enable the synchronous mode for seccomp notifications"),
> > OPT_END()
> > };
> >
> > --
> > 2.39.2
> >
--
- Arnaldo
prev parent reply other threads:[~2023-12-04 20:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-30 8:00 [PATCH][next] perf/benchmark: Fix spelling mistake "synchronious" -> "synchronous" Colin Ian King
2023-06-30 15:18 ` Ian Rogers
2023-12-04 20:26 ` Arnaldo Carvalho de Melo
2023-07-01 17:57 ` Namhyung Kim
2023-12-04 20:27 ` Arnaldo Carvalho de Melo [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=ZW42NiB4VK7Dp7oP@kernel.org \
--to=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=colin.i.king@gmail.com \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--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;
as well as URLs for NNTP newsgroup(s).