linux-edac.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@suse.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-edac <linux-edac@vger.kernel.org>,
	lkml <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] EDAC fixes for 5.2
Date: Thu, 16 May 2019 12:35:53 +0200	[thread overview]
Message-ID: <20190516103553.GA21457@zn.tnic> (raw)

Hi Linus,

please pull two EDAC fixes, as below.

Thx.

---
The following changes since commit 275b103a26e218b3d739e5ab15be6b40303a1428:

  Merge tag 'edac_for_5.2' of git://git.kernel.org/pub/scm/linux/kernel/git/bp/bp (2019-05-06 19:53:11 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/bp/bp.git tags/edac_fixes_for_5.2

for you to fetch changes up to 29a0c843973bc385918158c6976e4dbe891df969:

  EDAC/mc: Fix edac_mc_find() in case no device is found (2019-05-14 17:08:46 +0200)

----------------------------------------------------------------
* Do not build mpc85_edac as a module			(Michael Ellerman)

* Correct edac_mc_find()'s return value on error	(Robert Richter)

----------------------------------------------------------------
Michael Ellerman (1):
      EDAC/mpc85xx: Prevent building as a module

Robert Richter (1):
      EDAC/mc: Fix edac_mc_find() in case no device is found

 drivers/edac/Kconfig   |  4 ++--
 drivers/edac/edac_mc.c | 12 ++++--------
 2 files changed, 6 insertions(+), 10 deletions(-)

-- 
Regards/Gruss,
    Boris.

SUSE Linux GmbH, GF: Felix Imendörffer, Mary Higgins, Sri Rasiah, HRB 21284 (AG Nürnberg)

             reply	other threads:[~2019-05-16 10:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-16 10:35 Borislav Petkov [this message]
2019-05-16 19:25 ` [GIT PULL] EDAC fixes for 5.2 pr-tracker-bot

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=20190516103553.GA21457@zn.tnic \
    --to=bp@suse.de \
    --cc=linux-edac@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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).