linux-kernel - Re: Introduce interface to report BIOS bugs (reworked, FW

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <48B57074.40201@linux.intel.com>
Date:	Wed, 27 Aug 2008 17:19:16 +0200
From:	Andi Kleen <ak@...ux.intel.com>
To:	Thomas Renninger <trenn@...e.de>
CC:	bjorn.helgaas@...com, linux-kernel@...r.kernel.org,
	arjan@...ux.intel.com, linux-acpi@...r.kernel.org,
	ckornacker@...e.de
Subject: Re: Introduce interface to report BIOS bugs (reworked, FW_BUG simple
 solution)

Thomas Renninger wrote:
> Even simplier, using FW_BUG define. I agree that the first implementation
> was over-designed, I somehow liked the printk_fw_err() and printk_fw_info()
> more, looked somehow more consistent with:

Looks good to me now. The only issue is that the patchkit is cross subsystem
(cpufreq and ACPI). Either the patches go in through Andrew or we need
to figure out how to merge this.
-Andi
--
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/