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]
Message-ID: <575AE0F1.5020201@sr71.net>
Date:	Fri, 10 Jun 2016 08:46:57 -0700
From:	Dave Hansen <dave@...1.net>
To:	Jacob Pan <jacob.jun.pan@...ux.intel.com>,
	Vince Weaver <vincent.weaver@...ne.edu>
Cc:	hpa@...or.com, dave.hansen@...ux.intel.com, mingo@...nel.org,
	linux-kernel@...r.kernel.org, acme@...hat.com,
	peterz@...radead.org, jolsa@...hat.com, eranian@...gle.com,
	tglx@...utronix.de, luto@...capital.net, brgerst@...il.com,
	alexander.shishkin@...ux.intel.com, bp@...en8.de,
	torvalds@...ux-foundation.org, dvlasenk@...hat.com,
	linux-tip-commits@...r.kernel.org
Subject: Re: [tip:perf/core] perf/x86/rapl: Add Skylake server model detection

On 06/10/2016 05:35 AM, Jacob Pan wrote:
>> > code does not match git commit message.  The code says that skylake
>> > server matches the haswell server.  (Yes I know broadwell server
>> > apparently matches haswell server too, but you might want to say that
>> > in the git commit to avoid confusion).
>> > 
> Yes, it would be more clear to state that SKX matches BDX as well as
> HSX. I was following the order of product releases. Should I submit a
> patch for it? or can the commit message be changed by the maintainers?

Once it's been committed to git, maintainers can't change the commit
message without rebasing.

I wouldn't worry about it.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ