From: Ed Maste <emaste@freebsd.org>
To: Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>
Cc: linux-kernel@vger.kernel.org,
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@redhat.com>, Namhyung Kim <namhyung@kernel.org>,
Nick Hu <nickhu@andestech.com>, Greentime Hu <green.hu@gmail.com>,
Vincent Chen <deanbo422@gmail.com>,
Thomas Richter <tmricht@linux.ibm.com>
Subject: Re: [PATCH] perf list: remove name from L1D_RO_EXCL_WRITES description
Date: Fri, 13 Dec 2019 11:02:51 -0500 [thread overview]
Message-ID: <CAPyFy2A5+ftfNFUKZeV=dx-3TMkupnL_oJhR6Pu0JOuKUjOBMA@mail.gmail.com> (raw)
In-Reply-To: <20191212180213.GI13965@kernel.org>
On Thu, 12 Dec 2019 at 13:02, Arnaldo Carvalho de Melo
<arnaldo.melo@gmail.com> wrote:
>
> Em Thu, Dec 12, 2019 at 02:53:46PM +0000, Ed Maste escreveu:
> > From: Ed Maste <emaste@freebsd.org>
> >
> > In 7fcfa9a2d9 an unintended prefix "Counter:18 Name:" was removed from
> > the description for L1D_RO_EXCL_WRITES, but the extra name remained in
> > the description. Remove it too.
>
> Also trivially correct, applied and added a Fixes tag with that cset
> (7fcfa9a2d9).
>
> - Arnaldo
Thank you, and sorry that these came not as a set. Each time I thought
I had only one change to submit and then found another nit shortly
after I sent the previous.
There is one more related change that hasn't been picked up yet (and
that I seem to have missed adding you on CC), with subject
[PATCH] perf vendor events s390: Fix commas so PMU event files are valid JSON
next prev parent reply other threads:[~2019-12-13 20:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-12 14:53 [PATCH] perf list: remove name from L1D_RO_EXCL_WRITES description Ed Maste
2019-12-12 18:02 ` Arnaldo Carvalho de Melo
2019-12-13 16:02 ` Ed Maste [this message]
2019-12-17 11:31 ` [tip: perf/urgent] perf vendor events s390: Remove " tip-bot2 for Ed Maste
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='CAPyFy2A5+ftfNFUKZeV=dx-3TMkupnL_oJhR6Pu0JOuKUjOBMA@mail.gmail.com' \
--to=emaste@freebsd.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=arnaldo.melo@gmail.com \
--cc=deanbo422@gmail.com \
--cc=green.hu@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=nickhu@andestech.com \
--cc=peterz@infradead.org \
--cc=tmricht@linux.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.