Re: [tip:perf/core] perf/x86/rapl: Add Skylake server model detection
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- Subject: Re: [tip:perf/core] perf/x86/rapl: Add Skylake server model detection
- From: Dave Hansen <dave@xxxxxxxx>
- Date: Fri, 10 Jun 2016 08:46:57 -0700
- Cc: hpa@xxxxxxxxx, dave.hansen@xxxxxxxxxxxxxxx, mingo@xxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, acme@xxxxxxxxxx, peterz@xxxxxxxxxxxxx, jolsa@xxxxxxxxxx, eranian@xxxxxxxxxx, tglx@xxxxxxxxxxxxx, luto@xxxxxxxxxxxxxx, brgerst@xxxxxxxxx, alexander.shishkin@xxxxxxxxxxxxxxx, bp@xxxxxxxxx, torvalds@xxxxxxxxxxxxxxxxxxxx, dvlasenk@xxxxxxxxxx, linux-tip-commits@xxxxxxxxxxxxxxx
- In-reply-to: <20160610053547.731ea62d@yairi>
- User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0
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.
--
To unsubscribe from this list: send the line "unsubscribe linux-tip-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
[Index of Archives]
[Linux Stable Commits]
[Linux Stable Kernel]
[Linux Kernel]
[Linux USB Devel]
[Linux Video &Media]
[Linux Audio Users]
[Yosemite News]
[Linux SCSI]
