From: "Luck, Tony" <tony.luck@intel.com>
To: Marco Elver <elver@google.com>, "bp@alien8.de" <bp@alien8.de>,
"jbaron@akamai.com" <jbaron@akamai.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Mauro Carvalho Chehab" <mchehab@kernel.org>,
linux-edac <linux-edac@vger.kernel.org>
Subject: RE: [PATCH v2 2/2] EDAC, ie31200: Reformat PCI device table
Date: Mon, 10 Jun 2019 20:13:42 +0000 [thread overview]
Message-ID: <3908561D78D1C84285E8C5FCA982C28F7E996B42@ORSMSX104.amr.corp.intel.com> (raw)
In-Reply-To: <20190610191422.177931-2-elver@google.com>
> Reformat device table after Coffee Lake additions to be more readable.
I like that you put the reformat second ... if some old version needs a backport
to get Coffee Lake support they can just take part 1 to get the functionality
and then decide whether or not to take part 2.
Both parts:
Acked-by: Tony Luck <tony.luck@intel.com>
next prev parent reply other threads:[~2019-06-10 20:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-10 19:14 [PATCH v2 1/2] EDAC, ie31200: Add Intel Coffee Lake CPU support Marco Elver
2019-06-10 19:14 ` [PATCH v2 2/2] EDAC, ie31200: Reformat PCI device table Marco Elver
2019-06-10 20:13 ` Luck, Tony [this message]
2019-06-10 21:02 ` Borislav Petkov
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=3908561D78D1C84285E8C5FCA982C28F7E996B42@ORSMSX104.amr.corp.intel.com \
--to=tony.luck@intel.com \
--cc=bp@alien8.de \
--cc=elver@google.com \
--cc=jbaron@akamai.com \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@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).