[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <a2f55a9c-25fd-d79d-5f20-8144694f394d@roeck-us.net>
Date: Tue, 16 Jun 2020 07:46:36 -0700
From: Guenter Roeck <linux@...ck-us.net>
To: Borislav Petkov <bp@...en8.de>
Cc: Jacky Hu <hengqing.hu@...il.com>, linux-edac@...r.kernel.org,
linux-kernel@...r.kernel.org, tony.luck@...el.com, x86@...nel.org,
Yazen Ghannam <yazen.ghannam@....com>,
linux-hwmon@...r.kernel.org
Subject: Re: [PATCH 0/2] MCA and EDAC updates for AMD Family 17h, Model 60h
On 6/16/20 7:35 AM, Borislav Petkov wrote:
> On Mon, Jun 15, 2020 at 08:01:22AM -0700, Guenter Roeck wrote:
>> Looks like we may have to black-list current measurements
>> for that chip, though.
>>
>> Guenter
>>
>>>> Jacky Hu (2):
>>>> x86/amd_nb: Add Family 17h, Model 60h PCI IDs
>>>> EDAC/amd64: Add family ops for Family 17h Models 60h-6Fh
>>>>
>>>> arch/x86/kernel/amd_nb.c | 5 +++++
>>>> drivers/edac/amd64_edac.c | 14 ++++++++++++++
>>>> drivers/edac/amd64_edac.h | 3 +++
>>>> drivers/hwmon/k10temp.c | 2 ++
>
> ... meaning I should not take the k10temp changes yet? I can drop them
> and take the rest...
>
No, that is independent. It is more like a note to myself. I'll have to get
debug dumps from someone with affected chip(s), and for that to work
support for those chips has to be enabled in k10temp.
Thanks,
Guenter
Powered by blists - more mailing lists