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] [thread-next>] [day] [month] [year] [list]
Date:   Mon, 17 Oct 2016 14:26:47 -0700
From:   Andi Kleen <andi@...stfloor.org>
To:     Arnaldo Carvalho de Melo <acme@...nel.org>
Cc:     Sukadev Bhattiprolu <sukadev@...ux.vnet.ibm.com>,
        Andi Kleen <andi@...stfloor.org>,
        Ingo Molnar <mingo@...nel.org>, Jiri Olsa <jolsa@...nel.org>,
        Wang Nan <wangnan0@...wei.com>,
        Namhyung Kim <namhyung@...nel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [RFC] Vendor events file/dir names

On Mon, Oct 17, 2016 at 04:04:38PM -0300, Arnaldo Carvalho de Melo wrote:
> Hi,
> 
> 	Ingo pointed out to me that in the kernel sources we do not use
> file/dir names with uppercase chars (look, for instance, at arch/), so I
> mostly scripted a conversion to lowercase and what I got is at:
> 
>    git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux.git perf/vendor_events
>    
>    https://git.kernel.org/cgit/linux/kernel/git/acme/linux.git/log/?h=perf/vendor_events
> 
> 	I did test it on my Lenovo t450s (Broadwell) and got the same
> results as before, and the changed file and directory names don't get
> presented to the user AFAIK, so its just a matter of consistency with
> the existing practices in the kernel sources, no visible difference to
> users.
> 
> 	Please let me know if you have any technical argument against
> this move,

That's fine for me. 

-Andi

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ