From: Borislav Petkov <bp@alien8.de>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Jacky Hu <hengqing.hu@gmail.com>,
linux-edac@vger.kernel.org, linux-kernel@vger.kernel.org,
tony.luck@intel.com, x86@kernel.org,
Yazen Ghannam <yazen.ghannam@amd.com>,
linux-hwmon@vger.kernel.org
Subject: Re: [PATCH 0/2] MCA and EDAC updates for AMD Family 17h, Model 60h
Date: Tue, 16 Jun 2020 16:55:01 +0200 [thread overview]
Message-ID: <20200616145501.GI13515@zn.tnic> (raw)
In-Reply-To: <a2f55a9c-25fd-d79d-5f20-8144694f394d@roeck-us.net>
On Tue, Jun 16, 2020 at 07:46:36AM -0700, Guenter Roeck wrote:
> 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.
Ok, then, will take those patches as is.
Thx.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2020-06-16 14:55 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-07 4:37 [PATCH 0/2] MCA and EDAC updates for AMD Family 17h, Model 60h Jacky Hu
2020-06-07 4:37 ` [PATCH 1/2] x86/amd_nb: Add Family 17h, Model 60h PCI IDs Jacky Hu
2020-06-16 18:08 ` Borislav Petkov
2020-06-07 4:37 ` [PATCH 2/2] EDAC/amd64: Add family ops for Family 17h Models 60h-6Fh Jacky Hu
2020-06-16 18:09 ` Borislav Petkov
2020-06-17 1:32 ` [PATCH] hwmon: (k10temp) Add AMD family 17h model 60h probe Jacky Hu
2020-06-17 3:40 ` Guenter Roeck
2020-06-17 7:19 ` Jacky Hu
2020-06-17 14:33 ` Guenter Roeck
2020-06-17 14:55 ` Jacky Hu
2020-06-17 14:54 ` Alexander Monakov
2020-06-17 15:07 ` Jacky Hu
2020-06-17 15:22 ` Borislav Petkov
2020-06-15 11:59 ` [PATCH 0/2] MCA and EDAC updates for AMD Family 17h, Model 60h Borislav Petkov
2020-06-15 15:01 ` Guenter Roeck
2020-06-16 14:35 ` Borislav Petkov
2020-06-16 14:46 ` Guenter Roeck
2020-06-16 14:55 ` Borislav Petkov [this message]
2020-06-16 14:11 ` Yazen Ghannam
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200616145501.GI13515@zn.tnic \
--to=bp@alien8.de \
--cc=hengqing.hu@gmail.com \
--cc=linux-edac@vger.kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=tony.luck@intel.com \
--cc=x86@kernel.org \
--cc=yazen.ghannam@amd.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).