linux-kernel - Re: [PATCH 4/6] include linux pci_id-h add amd northbridge defines

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 for Android: free password hash cracker in your pocket

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

Date:	Mon, 11 Jun 2007 16:49:47 -0700
From:	Greg KH <greg@...ah.com>
To:	dougthompson@...ssion.com
Cc:	alan@...rguk.ukuu.org.uk, linux-kernel@...r.kernel.org,
	akpm@...l.org
Subject: Re: [PATCH 4/6] include linux pci_id-h add amd northbridge defines

On Mon, Jun 11, 2007 at 04:30:11PM -0700, Doug Thompson wrote:
> 
> --- Greg KH <greg@...ah.com> wrote:
> 
> > On Fri, Jun 08, 2007 at 10:45:10AM -0600, dougthompson@...ssion.com wrote:
> > > From:	Douglas Thompson <dougthompson@...ssion.com>
> > > 
> > > pci_ids.h needs two of the AMD NB device-ids namely,
> > > Addressmap and the Memory Controller devices
> > 
> > Does any kernel driver need this?  We're trying to only include things
> > in the pci_ids.h file that are needed in more than one file to cut down
> > on the churn here for unnecessary ids.
> 
> not at the moment, but I have the k8_edac.c EDAC driver in my queue, which was in the -mm tree but
> I had to pull it back once.
> 
> I am working with the k8 driver and its dealing with a race with the mcelog device as both access
> the K8 NB. The K8 driver does use these regs and it currently has #ifndef s in it for both of
> them.
> 
> I guess I could have submitted the patch when the K8 driver was submitted.

That would be preferable, thanks.

greg k-h
-
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/