All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Luck, Tony" <tony.luck@intel.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linux-edac@vger.kernel.org,
	Borislav Petkov <bp@suse.de>, Ingo Molnar <mingo@kernel.org>
Subject: [GIT PULL] Fix mcelog regression
Date: Tue, 17 Feb 2015 13:59:46 -0800	[thread overview]
Message-ID: <54e3b9d24385bb413@agluck-desk.sc.intel.com> (raw)

Sorry for bypassing normal channels, but this looks like a trivial
regression fix to me, but I'm getting pushback from my co-maintainer
and from Ingo.

  1. This used to work
  2. Now it doesn't
  3. People have complained

Previous threads:
  https://lkml.org/lkml/2015/1/30/641
  https://lkml.org/lkml/2015/2/11/437

The following changes since commit bfa76d49576599a4b9f9b7a71f23d73d6dcff735:

  Linux 3.19 (2015-02-08 18:54:22 -0800)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/ras/ras.git tags/please-pull-fixmcelog

for you to fetch changes up to a2413d8b2982fb6823cdb66704938a9a345d0a7d:

  x86/mce: Fix regression. All error records should report via /dev/mcelog (2015-02-09 09:36:53 -0800)

----------------------------------------------------------------
Fix regression - functions on the mce notifier chain should
not be able to decide that an event should not be logged

----------------------------------------------------------------
Tony Luck (1):
      x86/mce: Fix regression. All error records should report via /dev/mcelog

 arch/x86/kernel/cpu/mcheck/mce.c | 5 +----
 1 file changed, 1 insertion(+), 4 deletions(-)

             reply	other threads:[~2015-02-17 22:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-17 21:59 Luck, Tony [this message]
2015-02-18  6:41 ` [GIT PULL] Fix mcelog regression Ingo Molnar

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=54e3b9d24385bb413@agluck-desk.sc.intel.com \
    --to=tony.luck@intel.com \
    --cc=bp@suse.de \
    --cc=linux-edac@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.