Date:   Mon, 23 Jan 2023 10:10:33 -0300
From:   Arnaldo Carvalho de Melo <acme@kernel.org>
To:     Diederik de Haas <didi.debian@cknow.org>
Cc:     Edward <edward.baker@intel.com>, Ian Rogers <irogers@google.com>,
        Peter Zijlstra <peterz@infradead.org>,
        Ingo Molnar <mingo@redhat.com>,
        "open list:PERFORMANCE EVENTS SUBSYSTEM" 
        <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] tools/perf: Various spelling fixes
Message-ID: <Y86HSc3YlwrE4f4B@kernel.org>
References: <20230121184648.38487-1-didi.debian@cknow.org>
 <CAP-5=fX1-3ZnXk8G2fB0q9F3MjjA+zWWm1LbuYGc5nL5v3bXYg@mail.gmail.com>
 <3632669.kckeHSHuci@prancing-pony>
 <8858063.18A79QhPUa@prancing-pony>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <8858063.18A79QhPUa@prancing-pony>
Precedence: bulk

Em Sun, Jan 22, 2023 at 01:37:11PM +0100, Diederik de Haas escreveu:
> 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

I just applied it, thanks.

- Arnaldo
 
> 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