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: Jason Baron <jbaron@akamai.com>,
	linux-edac <linux-edac@vger.kernel.org>,
	lkml <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] EDAC fixes for 3.18
Date: Mon, 27 Oct 2014 15:32:37 +0100	[thread overview]
Message-ID: <20141027143236.GA4741@pd.tnic> (raw)

Hi Linus,

please pull a bunch of fixes from Jason.

Thanks.

---
The following changes since commit f114040e3ea6e07372334ade75d1ee0775c355e1:

  Linux 3.18-rc1 (2014-10-19 18:08:38 -0700)

are available in the git repository at:

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

for you to fetch changes up to 8030122a9ccf939186f8db96c318dbb99b5463f6:

  e7xxx_edac: Report CE events properly (2014-10-22 22:59:00 +0200)

----------------------------------------------------------------
Correct severity of reported errors in several EDAC drivers. From Jason
Baron.

----------------------------------------------------------------
Jason Baron (4):
      i3200_edac: Report CE events properly
      i82860_edac: Report CE events properly
      cpc925_edac: Report UE events properly
      e7xxx_edac: Report CE events properly

 drivers/edac/cpc925_edac.c | 2 +-
 drivers/edac/e7xxx_edac.c  | 2 +-
 drivers/edac/i3200_edac.c  | 4 ++--
 drivers/edac/i82860_edac.c | 2 +-
 4 files changed, 5 insertions(+), 5 deletions(-)

-- 
Regards/Gruss,
    Boris.

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

             reply	other threads:[~2014-10-27 14:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-27 14:32 Borislav Petkov [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-10-06 11:00 [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=20141027143236.GA4741@pd.tnic \
    --to=bp@suse.de \
    --cc=jbaron@akamai.com \
    --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