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]
Message-ID: <db9a9449-03f9-ee83-ea4d-e2e0bccd482f@roeck-us.net>
Date:   Tue, 27 Mar 2018 03:23:10 -0700
From:   Guenter Roeck <linux@...ck-us.net>
To:     Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        Thomas Backlund <tmb@...eia.org>
Cc:     Kash Pande <kash@...pleback.net>, linux-kernel@...r.kernel.org,
        torvalds@...ux-foundation.org, akpm@...ux-foundation.org,
        shuahkh@....samsung.com, patches@...nelci.org,
        ben.hutchings@...ethink.co.uk, lkft-triage@...ts.linaro.org,
        stable@...r.kernel.org
Subject: Re: [PATCH 4.14 000/109] 4.14.28-stable review

On 03/27/2018 01:45 AM, Greg Kroah-Hartman wrote:
> On Tue, Mar 27, 2018 at 11:33:00AM +0300, Thomas Backlund wrote:
>> Den 27.03.2018 kl. 09:37, skrev Guenter Roeck:
>>> On 03/26/2018 11:28 PM, Greg Kroah-Hartman wrote:
>>>> On Mon, Mar 26, 2018 at 01:54:18PM -0400, Kash Pande wrote:
>>>>> On 2018-03-19 02:20 PM, Guenter Roeck wrote:
>>>>>> Ryzen and Threadripper are only supported in v4.15+.
>>>>>
>>>>>
>>>>> Nope, the offset for 1900X is not available in 4.15, I've had to
>>>>> manually patch all systems otherwise monitoring complains they
>>>>> idle at 53C.
>>>>
>>>> I don't understand, what patch are you talking about here?
>>>>
>>>
>>> 6509614fdd2d, but you'll also want aef17ca12719 if that isn't queued
>>> already.
>>>
>>> Guenter
>>>
>>
>> And if you ant it to work in 4.14 longterm, you want the series:
>>
>> 68546abf7a3a63f199e53d6dcaa7375df37a6aaa  hwmon: (k10temp) Move chip
>> specific code into probe function
>> 9af0a9aecdb945cd5513941ffdcbcc031009b402  hwmon: (k10temp) Add support for
>> family 17h
>> 1b50b776355fa6c6d7b3281a63c275d5c18d629d  hwmon: (k10temp) Add support for
>> temperature offsets
>> ab5ee24615f9dd8b0cd199403959f8b13309e7b1  hwmon: (k10temp) Correct model
>> name for Ryzen 1600X
>> 6509614fdd2d05c6926d50901a45d5dfb852b715  hwmon: (k10temp) Add temperature
>> offset for Ryzen 1900X
>> aef17ca1271948ee57cc39b2493d31110cc42625  hwmon: (k10temp) Only apply
>> temperature offset if result is positive
>>
>>
>> We have it in Mageia, and I've confirmed it works on a Ryzen 7 1700 and
>> ThreadRipper 1950X
> 
> I'd like an ack from the hwmon maintainer before adding all of those, as
> it really feels like a "backport new hardware support" type of request
> that is a bit bigger than a normal "add some new device ids and quirks".
> 
That is why I did not request it. It is ok with me if you are willing to
accept it, though.

Guenter

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ