lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:   Mon, 23 Jan 2023 09:24:08 -0800
From:   Ian Rogers <irogers@...gle.com>
To:     Diederik de Haas <didi.debian@...ow.org>
Cc:     Edward <edward.baker@...el.com>,
        Peter Zijlstra <peterz@...radead.org>,
        Ingo Molnar <mingo@...hat.com>,
        Arnaldo Carvalho de Melo <acme@...nel.org>,
        "open list:PERFORMANCE EVENTS SUBSYSTEM" 
        <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] tools/perf: Various spelling fixes

On Sun, Jan 22, 2023 at 4:37 AM Diederik de Haas <didi.debian@...ow.org> wrote:
>
> 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

Thanks Diederik! There are some updates from Intel's perfmon
repository that we should pull to the perf tool pre 6.3. I believe
there is an update pending for typo fixes and hopefully these can
include yours. I'll try to keep an eye on things and send them to LKML
unless somebody beats me. Thanks Arnaldo for pulling the other change.

Ian

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ