From: Aravind Gopalakrishnan <Aravind.Gopalakrishnan@amd.com>
To: <bp@alien8.de>, <mchehab@osg.samsung.com>, <dougthompson@xmission.com>
Cc: <linux-edac@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: [PATCH 0/3] Updates to amd64_edac and ghes_edac
Date: Wed, 16 Sep 2015 15:53:28 -0500 [thread overview]
Message-ID: <1442436811-23382-1-git-send-email-Aravind.Gopalakrishnan@amd.com> (raw)
Patch 1: Cleanup patch to remove redundant definiton of memory types.
No functional change introduced
Patch 2: For F15hM60h, register used to program scrub rate has changed.
Add support in the code for the new register
Patch 3: Update comments section regarding copyright and documentation info
No functional change here.
Aravind Gopalakrishnan (3):
EDAC, ghes_edac: Remove redundant memory_type array
EDAC, amd64_edac: Extend scrub rate programmability feature for
F15hM60h
EDAC, amd64_edac: Update copyright and documentation info
drivers/edac/amd64_edac.c | 53 ++++++++++++++++++++++++++++++++++++++---------
drivers/edac/amd64_edac.h | 33 +++++++++++++++++++++++++++--
drivers/edac/ghes_edac.c | 22 +-------------------
3 files changed, 75 insertions(+), 33 deletions(-)
--
2.5.0
next reply other threads:[~2015-09-16 20:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-16 20:53 Aravind Gopalakrishnan [this message]
2015-09-16 20:53 ` [PATCH 1/3] EDAC, ghes_edac: Remove redundant memory_type array Aravind Gopalakrishnan
2015-09-24 9:24 ` Borislav Petkov
2015-09-16 20:53 ` [PATCH 2/3] EDAC, amd64_edac: Extend scrub rate programmability feature for F15hM60h Aravind Gopalakrishnan
2015-09-24 9:18 ` Borislav Petkov
2015-09-24 16:15 ` Aravind Gopalakrishnan
2015-09-24 16:33 ` Borislav Petkov
2015-09-24 16:42 ` Aravind Gopalakrishnan
2015-09-16 20:53 ` [PATCH 3/3] EDAC, amd64_edac: Update copyright and documentation info Aravind Gopalakrishnan
2015-09-17 7:43 ` Borislav Petkov
2015-09-17 14:35 ` Aravind Gopalakrishnan
2015-09-17 15:24 ` Borislav Petkov
2015-09-17 15:33 ` Aravind Gopalakrishnan
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=1442436811-23382-1-git-send-email-Aravind.Gopalakrishnan@amd.com \
--to=aravind.gopalakrishnan@amd.com \
--cc=bp@alien8.de \
--cc=dougthompson@xmission.com \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@osg.samsung.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
all inboxes | Powered by JetHome®