linux-kernel - Re: [PATCH 0/2] x86, MCE: Use MCE decoder notifier chain

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20110805103512.GH2420@elte.hu>
Date:	Fri, 5 Aug 2011 12:35:12 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Borislav Petkov <bp@...64.org>
Cc:	Mauro Carvalho Chehab <mchehab@...hat.com>,
	Tony Luck <tony.luck@...el.com>,
	EDAC devel <linux-edac@...r.kernel.org>,
	X86-ML <x86@...nel.org>, LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 0/2] x86, MCE: Use MCE decoder notifier chain


* Borislav Petkov <bp@...64.org> wrote:

> On Thu, Aug 04, 2011 at 08:56:58PM -0400, Mauro Carvalho Chehab wrote:
> > Boris,
> > 
> > Em 02-08-2011 08:58, Borislav Petkov escreveu:
> > > Ping?
> > > 
> > > Mauro, any progress on those below?
> > 
> > Sorry for taking a long time on that. I'm testing it right now, together with
> > a few other patches for i7core.
> > 
> > I've added it (with a few conflict fixes) at:
> > 	ssh://master.kernel.org/pub/scm/linux/kernel/git/mchehab/edac.git  linux_next
> > 
> > If everything works as before, I'll send it to Linus tomorrow, assuming that
> > linux-next will catch them.
> 
> Ok, thanks.
> 
> Please bear in mind that the second patch depends on the first and
> they both touch arch/x86 so you'd at least need Acked-by's from x86
> maintainers. Ingo?

a quick look suggests it's ok:

Acked-by: Ingo Molnar <mingo@...e.hu>

Thanks,

	Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/