public inbox for linux-kernel@vger.kernel.org
 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 3.18
Date: Mon, 6 Oct 2014 13:00:26 +0200	[thread overview]
Message-ID: <20141006110026.GC4372@pd.tnic> (raw)

Hi Linus,

here's the small queue of EDAC fixes which has been accumulating.

The mpc85xx_edac fix is tagged for stable but since it got confirmed
only days before the final 3.17 release, I didn't rush a last minute
pull request to you. I hope that's ok as it will trickle down to stable
anyway and we'll make sure it lands in 3.17-stable too.

Thanks.

---
The following changes since commit 52addcf9d6669fa439387610bc65c92fa0980cef:

  Linux 3.17-rc2 (2014-08-25 15:36:20 -0700)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/bp/bp.git tags/edac_for_3.18

for you to fetch changes up to a18c3f16a907b8977ef65fc8dd71ed3f7b751748:

  mpc85xx_edac: Make L2 interrupt shared too (2014-09-30 12:55:41 +0200)

----------------------------------------------------------------
Misc small fixes/improvements accumulated from the summer months,
nothing earth-shattering.

----------------------------------------------------------------
Aravind Gopalakrishnan (1):
      amd64_edac: Modify usage of amd64_read_dct_pci_cfg()

Borislav Petkov (2):
      EDAC: Fix mem_types strings type
      mpc85xx_edac: Make L2 interrupt shared too

Pranith Kumar (1):
      ppc4xx_edac: Fix build error caused by wrong member access

 drivers/edac/amd64_edac.c   | 146 ++++++++++++++++++++++++--------------------
 drivers/edac/amd64_edac.h   |   5 --
 drivers/edac/edac_core.h    |   2 +-
 drivers/edac/edac_mc.c      |   2 +-
 drivers/edac/mpc85xx_edac.c |   2 +-
 drivers/edac/ppc4xx_edac.c  |   2 +-
 6 files changed, 84 insertions(+), 75 deletions(-)

-- 
Regards/Gruss,
    Boris.

Sent from a fat crate under my desk. Formatting is fine.
--

             reply	other threads:[~2014-10-06 11:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-06 11:00 Borislav Petkov [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-10-27 14:32 [GIT PULL] EDAC fixes for 3.18 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=20141006110026.GC4372@pd.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