From: Borislav Petkov <bp@alien8.de>
To: Kim Phillips <kphillips@amd.com>
Cc: "Ghannam, Yazen" <Yazen.Ghannam@amd.com>,
"linux-edac@vger.kernel.org" <linux-edac@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 1/6] EDAC/amd64: Add Family 17h Model 30h PCI IDs
Date: Fri, 22 Mar 2019 17:46:30 +0100 [thread overview]
Message-ID: <20190322164630.GH12472@zn.tnic> (raw)
In-Reply-To: <ca64e38b-b374-288e-1399-c8e8598fc91c@amd.com>
On Fri, Mar 22, 2019 at 04:33:48PM +0000, Kim Phillips wrote:
> Hi Boris,
>
> I've tested this patch and it gets rid of a slew of these messages:
>
> kernel: EDAC amd64: Error: F0 not found, device 0x1460 (broken BIOS?)
> kernel: EDAC amd64: Error: Error probing instance: 0
>
> So please add my:
>
> Tested-by: Kim Phillips <kim.phillips@amd.com>
>
> Thank you,
Thanks but please do not top-post when replying to mails on public
mailing lists.
--
Regards/Gruss,
Boris.
Good mailing practices for 400: avoid top-posting and trim the reply.
prev parent reply other threads:[~2019-03-22 16:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-28 15:36 Ghannam, Yazen
2019-02-28 15:36 ` [PATCH v3 3/6] EDAC/amd64: Support more than two Unified Memory Controllers Ghannam, Yazen
2019-03-23 12:15 ` Borislav Petkov
2019-03-23 17:22 ` Ghannam, Yazen
2019-02-28 15:36 ` [PATCH v3 2/6] EDAC/amd64: Use a macro for iterating over " Ghannam, Yazen
2019-02-28 15:36 ` [PATCH v3 4/6] EDAC/amd64: Recognize x16 Symbol Size Ghannam, Yazen
2019-02-28 15:36 ` [PATCH v3 5/6] EDAC/amd64: Support more than two Controllers for Chip Select handling Ghannam, Yazen
2019-02-28 15:36 ` [PATCH v3 6/6] EDAC/amd64: Adjust printed Chip Select sizes when interleaved Ghannam, Yazen
2019-03-21 20:30 ` [PATCH v3 1/6] EDAC/amd64: Add Family 17h Model 30h PCI IDs Ghannam, Yazen
2019-03-22 16:33 ` Kim Phillips
2019-03-22 16:46 ` Borislav Petkov [this message]
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=20190322164630.GH12472@zn.tnic \
--to=bp@alien8.de \
--cc=Yazen.Ghannam@amd.com \
--cc=kphillips@amd.com \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®