From: "Luck, Tony" <tony.luck@intel.com>
To: Borislav Petkov <bp@alien8.de>
Cc: 'Aristeu Rozanski' <aris@redhat.com>,
"'linux-edac@vger.kernel.org'" <linux-edac@vger.kernel.org>,
'Mauro Carvalho Chehab' <mchehab@kernel.org>
Subject: Re: [PATCH] EDAC: skx_common: downgrade message importance on missing PCI device
Date: Tue, 7 Jan 2020 13:43:10 -0800 [thread overview]
Message-ID: <20200107214310.GA31851@agluck-desk2.amr.corp.intel.com> (raw)
In-Reply-To: <20200107164528.GD29542@zn.tnic>
On Tue, Jan 07, 2020 at 05:45:28PM +0100, Borislav Petkov wrote:
> On Tue, Jan 07, 2020 at 10:51:09AM -0500, 'Aristeu Rozanski' wrote:
> > On Mon, Jan 06, 2020 at 05:23:06PM +0100, Borislav Petkov wrote:
> > > I'm not saying you should blindly remove them. They might be useful for
> > > debugging purposes so you should consider that usage angle first. In the
> > > AMD case, the message was really useless.
> >
> > Ah, I thought you had an objection to this patch :)
> > Do you mind considering it for inclusion?
>
> That's Tony's call as he's maintaining the Intel side of EDAC.
Already applied to git://git.kernel.org/pub/scm/linux/kernel/git/ras/ras.git
in edac-for-next branch. Sorry, should have sent you an "Applied" message.
-Tony
next prev parent reply other threads:[~2020-01-07 21:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-04 21:23 [PATCH] EDAC: skx_common: downgrade message importance on missing PCI device Aristeu Rozanski
2019-12-09 21:52 ` Luck, Tony
2019-12-10 0:02 ` Luck, Tony
2019-12-10 9:00 ` Borislav Petkov
2020-01-06 15:12 ` 'Aristeu Rozanski'
2020-01-06 16:17 ` Borislav Petkov
2020-01-06 16:20 ` 'Aristeu Rozanski'
2020-01-06 16:23 ` Borislav Petkov
2020-01-07 15:51 ` 'Aristeu Rozanski'
2020-01-07 16:45 ` Borislav Petkov
2020-01-07 21:43 ` Luck, Tony [this message]
2020-01-08 14:54 ` 'Aristeu Rozanski'
2019-12-10 14:18 ` 'Aristeu Rozanski'
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=20200107214310.GA31851@agluck-desk2.amr.corp.intel.com \
--to=tony.luck@intel.com \
--cc=aris@redhat.com \
--cc=bp@alien8.de \
--cc=linux-edac@vger.kernel.org \
--cc=mchehab@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;
as well as URLs for NNTP newsgroup(s).