linux-kernel - Re: [PATCH 1/2] pci: add misrouted interrupt error handling

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: <200808041620.35487.bjorn.helgaas@hp.com>
Date:	Mon, 4 Aug 2008 16:20:35 -0600
From:	Bjorn Helgaas <bjorn.helgaas@...com>
To:	Matthew Wilcox <matthew@....cx>
Cc:	James Bottomley <James.Bottomley@...senpartnership.com>,
	linux-scsi <linux-scsi@...r.kernel.org>,
	linux-kernel <linux-kernel@...r.kernel.org>,
	linux-pci@...r.kernel.org
Subject: Re: [PATCH 1/2] pci: add misrouted interrupt error handling

On Monday 04 August 2008 03:35:35 pm Matthew Wilcox wrote:
> On Mon, Aug 04, 2008 at 02:43:20PM -0600, Bjorn Helgaas wrote:
> > I tried to standardize the PCI core on "[%04x/%04x]" for vendor/device ID.
> 
> That's unfortunately different from lspci -nn:
> 
> 00:00.0 Host bridge [0600]: Intel Corporation Mobile PM965/GM965/GL960
> Memory Controller Hub [8086:2a00] (rev 03)
> 
> Sorry, I should have reviewed your patches ;-(

I can change those.  I just copied what seemed to be the most
prevalent.  But lspci is harder to change, so we should probably
follow that.
--
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/