linux-kernel - Re: [PATCH] fix x86 DMI checks for PCI quirks

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: <20080502115611.GA15645@auslistsprd01.us.dell.com>
Date:	Fri, 2 May 2008 06:56:11 -0500
From:	Matt Domsch <Matt_Domsch@...l.com>
To:	Arjan van de Ven <arjan@...radead.org>
Cc:	akpm@...ux-foundation.org, jgarzik@...ox.com, muli@...ibm.com,
	davej@...hat.com, tglx@...utronix.de, mingo@...hat.com,
	hpa@...or.com, bunk@...nel.org, linux-bugs@...l.com,
	linux-kernel@...r.kernel.org, greg@...ah.com
Subject: Re: [PATCH] fix x86 DMI checks for PCI quirks

On Thu, May 01, 2008 at 04:23:13AM -0700, Arjan van de Ven wrote:
> On Thu, 1 May 2008 21:54:27 -0500
> Matt Domsch <Matt_Domsch@...l.com> wrote:
> > 
> > This patch moves the DMI tests into its own file, arch/x86/pci/dmi.c,
> > and invokes them via subsys_initcall() before pci_acpi_init(),
> > pci_legacy_init(), and pcibios_init() are called, which may rely upon
> > these tests having been executed.
> 
> 
> Hi,
> 
> can we name this file something with "quirks" in it (dmi_quirks.c or
> so)? At least I tend to look for files named like that when searching
> for places that do specific hardware/machine based workarounds... 

sure, the file name matters not much to me in this regard, and I can
see your point.

-- 
Matt Domsch
Linux Technology Strategist, Dell Office of the CTO
linux.dell.com & www.dell.com/linux
--
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/