From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Thomas Richter <tmricht@linux.ibm.com>
Cc: linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
sumanthk@linux.ibm.com, svens@linux.ibm.com, gor@linux.ibm.com,
hca@linux.ibm.com
Subject: Re: [PATCH v3] perf report: Add s390 raw data interpretation for PAI counters
Date: Fri, 10 Nov 2023 10:33:46 -0300 [thread overview]
Message-ID: <ZU4xOmhlT5IQlI2O@kernel.org> (raw)
In-Reply-To: <6d5a8310-d3e4-4fa7-8103-b50b100e22f7@linux.ibm.com>
Em Fri, Nov 10, 2023 at 01:31:59PM +0100, Thomas Richter escreveu:
> On 11/10/23 13:10, Arnaldo Carvalho de Melo wrote:
> > Em Fri, Nov 10, 2023 at 12:09:08PM +0100, Thomas Richter escreveu:
> >> commit 1bf54f32f525 ("s390/pai: Add support for cryptography counters")
> > Where is this commit?
> > ⬢[acme@toolbox perf-tools-next]$ git show 1bf54f32f525
> > fatal: ambiguous argument '1bf54f32f525': unknown revision or path not in the working tree.
> > Use '--' to separate paths from revisions, like this:
> > 'git <command> [<revision>...] -- [<file>...]'
> > ⬢[acme@toolbox perf-tools-next]$
> > Looking using the description I get:
> > 39d62336f5c126ad s390/pai: add support for cryptography counters
> > Is this the one?
> Yep, I apologise for the cut & paste error, this is the commit number in question.
> Should I reset a corrected version?
I can fix this up, thanks for confirming,
- Arnaldo
next prev parent reply other threads:[~2023-11-10 13:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-10 11:09 [PATCH v3] perf report: Add s390 raw data interpretation for PAI counters Thomas Richter
2023-11-10 12:10 ` Arnaldo Carvalho de Melo
2023-11-10 12:31 ` Thomas Richter
2023-11-10 13:33 ` Arnaldo Carvalho de Melo [this message]
2023-11-11 12:10 ` Arnaldo Carvalho de Melo
2023-11-15 17:59 ` Arnaldo Carvalho de Melo
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=ZU4xOmhlT5IQlI2O@kernel.org \
--to=acme@kernel.org \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=sumanthk@linux.ibm.com \
--cc=svens@linux.ibm.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox