From: Diederik de Haas <didi.debian@cknow.org>
To: Edward <edward.baker@intel.com>, Ian Rogers <irogers@google.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
"open list:PERFORMANCE EVENTS SUBSYSTEM"
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] tools/perf: Various spelling fixes
Date: Sun, 22 Jan 2023 13:37:11 +0100 [thread overview]
Message-ID: <8858063.18A79QhPUa@prancing-pony> (raw)
In-Reply-To: <3632669.kckeHSHuci@prancing-pony>
[-- Attachment #1: Type: text/plain, Size: 1211 bytes --]
Hi Ian,
On Saturday, 21 January 2023 21:53:51 CET Diederik de Haas wrote:
> On Saturday, 21 January 2023 20:25:46 CET Ian Rogers wrote:
> > The JSON files are generated from Intel information here:
> > https://github.com/intel/perfmon/
> > Fixing the spelling in the tree means that when we update the
> > incorrect spelling will be generated again. Intel are looking at the
> > matter, I've added Edward Baker to the e-mail. To make it clearer,
> > could you separate the JSON fixes from the tool fixes?
>
> Yes, I'll send a v2 patch with the JSON files excluded.
> And I'll send a PR to the GH repo.
I just did send v2 of the patch with the following command:
git send-email --annotate -v2 HEAD~1 --to-cmd=scripts/get_maintainer.pl
But that no longer included you(r email)*, so here's the link:
https://lore.kernel.org/lkml/20230122122034.48020-1-didi.debian@cknow.org/
The PR on GH is here: https://github.com/intel/perfmon/pull/44
*) Still need to figure out how to properly use `git send-email` as I find the
separation of the email contents and then only subsequently and separately
seeing the To/CC list rather inconvenient.
Guess I'll just use --to=/--cc= manually for now.
Cheers,
Diederik
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2023-01-22 12:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-21 18:46 [PATCH] tools/perf: Various spelling fixes Diederik de Haas
2023-01-21 19:25 ` Ian Rogers
2023-01-21 20:53 ` Diederik de Haas
2023-01-22 12:37 ` Diederik de Haas [this message]
2023-01-23 13:10 ` Arnaldo Carvalho de Melo
2023-01-23 17:24 ` Ian Rogers
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=8858063.18A79QhPUa@prancing-pony \
--to=didi.debian@cknow.org \
--cc=acme@kernel.org \
--cc=edward.baker@intel.com \
--cc=irogers@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--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