linux-kernel - Re: [GIT PATCH] PCI patches for 2.6.24-rc1

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]

Date:	Mon, 5 Nov 2007 14:13:58 -0800 (PST)
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Greg KH <gregkh@...e.de>
cc:	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org, linux-pci@...ey.karlin.mff.cuni.cz,
	pcihpd-discuss@...ts.sourceforge.net
Subject: Re: [GIT PATCH] PCI patches for 2.6.24-rc1



On Mon, 5 Nov 2007, Greg KH wrote:
> 
> They are a bunch of quirk updates from David Miller, a new config item
> to help Jeff Garzik start to cleanup the isdn drivers and let him take
> those patches through his tree, and a few other minor bugfixes.

This one is bogus:

    PCI: Revert "PCI: disable MSI by default on systems with Serverworks HT1000 chips"
    
    This reverts commit e3008dedff4bdc96a5f67224cd3d8d12237082a0.
    
    The real bug was an INTX issue in the tg3 ethernet chip, and
    cured by commit c129d962a66c76964954a98b38586ada82cf9381
    
    Signed-off-by: David S. Miller <davem@...emloft.net>
    Acked-by: Jeff Garzik <jgarzik@...hat.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@...e.de>

It says "cured by commit c129d962a66c76964954a98b38586ada82cf9381", but no 
such commit exists. What?

Did you mean commit ba698ad4b7e466cbb4a8bde6b9da8080ab06808d, and if so, 
where did that c129d.. come from?

		Linus
-
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/