linux-edac.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hanna Hawa <hhhawa@amazon.com>
To: <bp@alien8.de>, <mchehab@kernel.org>, <james.morse@arm.com>,
	<rrichter@marvell.com>
Cc: <linux-edac@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<dwmw@amazon.co.uk>, <benh@amazon.com>, <ronenk@amazon.com>,
	<talel@amazon.com>, <jonnyc@amazon.com>, <hanochu@amazon.com>,
	<hhhawa@amazon.com>
Subject: [PATCH v3 0/2] Add an API for edac device, for mulriple errors
Date: Thu, 19 Sep 2019 18:17:11 +0100	[thread overview]
Message-ID: <20190919171713.8060-1-hhhawa@amazon.com> (raw)

Add an API for EDAC device to report for multiple errors, and move the
old report function to use the new API.

Changes from v2:
----------------
- Remove copy of edac_device_handle_*() functions, modify the existing
functions.

Changes from v1:
----------------
- use 'unsigned int' instead of u16
- update variable name to be count
- remove WARN_ON and simply exit if count is zero
- add inline functions in header file

Hanna Hawa (2):
  edac: Add an API for edac device to report for multiple errors
  edac: move edac_device_handle_*() API functions to header

 drivers/edac/edac_device.c | 50 +++++++++++++++++-------------
 drivers/edac/edac_device.h | 63 ++++++++++++++++++++++++++++----------
 2 files changed, 76 insertions(+), 37 deletions(-)

-- 
2.17.1


             reply	other threads:[~2019-09-19 17:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-19 17:17 Hanna Hawa [this message]
2019-09-19 17:17 ` [PATCH v3 1/2] edac: Add an API for edac device to report for multiple errors Hanna Hawa
2019-09-20  6:42   ` Robert Richter
2019-09-23 19:01     ` Hawa, Hanna
2019-09-21 15:28   ` kbuild test robot
2019-09-19 17:17 ` [PATCH v3 2/2] edac: move edac_device_handle_*() API functions to header Hanna Hawa
2019-09-20  6:49   ` Robert Richter
2019-09-23 19:01     ` Hawa, Hanna

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=20190919171713.8060-1-hhhawa@amazon.com \
    --to=hhhawa@amazon.com \
    --cc=benh@amazon.com \
    --cc=bp@alien8.de \
    --cc=dwmw@amazon.co.uk \
    --cc=hanochu@amazon.com \
    --cc=james.morse@arm.com \
    --cc=jonnyc@amazon.com \
    --cc=linux-edac@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=ronenk@amazon.com \
    --cc=rrichter@marvell.com \
    --cc=talel@amazon.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).