From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: James Clark <james.clark@arm.com>
Cc: Nick Forrington <nick.forrington@arm.com>,
linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>, Namhyung Kim <namhyung@kernel.org>,
Ian Rogers <irogers@google.com>,
Adrian Hunter <adrian.hunter@intel.com>,
Arnaldo Carvalho de Melo <acme@redhat.com>
Subject: Re: [PATCH] tools/perf: Fix man page formatting for perf lock
Date: Thu, 30 Nov 2023 10:38:42 -0300 [thread overview]
Message-ID: <ZWiQYvoxkOHy5mT8@kernel.org> (raw)
In-Reply-To: <e1e6641a-fec1-0b94-f57f-10ddec5b079c@arm.com>
Em Tue, Nov 28, 2023 at 11:08:54AM +0000, James Clark escreveu:
>
>
> On 02/11/2023 16:11, Nick Forrington wrote:
> > This makes "CONTENTION" a top level section (rather than a subsection of
> > "INFO").
> >
> > Fixes: 79079f21f50a ("perf lock: Add -k and -F options to 'contention' subcommand")
> > Signed-off-by: Nick Forrington <nick.forrington@arm.com>
> > ---
> > tools/perf/Documentation/perf-lock.txt | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/tools/perf/Documentation/perf-lock.txt b/tools/perf/Documentation/perf-lock.txt
> > index 503abcba1438..f5938d616d75 100644
> > --- a/tools/perf/Documentation/perf-lock.txt
> > +++ b/tools/perf/Documentation/perf-lock.txt
> > @@ -119,7 +119,7 @@ INFO OPTIONS
> >
> >
> > CONTENTION OPTIONS
> > ---------------
> > +------------------
> >
> > -k::
> > --key=<value>::
>
> Reviewed-by: James Clark <james.clark@arm.com>
Thanks, applied to perf-tools-next.
- Arnaldo
prev parent reply other threads:[~2023-11-30 13:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-02 16:11 [PATCH] tools/perf: Fix man page formatting for perf lock Nick Forrington
2023-11-02 23:45 ` Ian Rogers
2023-11-28 11:08 ` James Clark
2023-11-30 13:38 ` 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=ZWiQYvoxkOHy5mT8@kernel.org \
--to=acme@kernel.org \
--cc=acme@redhat.com \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=irogers@google.com \
--cc=james.clark@arm.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=namhyung@kernel.org \
--cc=nick.forrington@arm.com \
/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).