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:42:15 -0800 (PST)
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Greg KH <gregkh@...e.de>
cc:	davem@...emloft.net, jgarzik@...hat.com,
	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:
> 
> I'm guessing that David is referring to a commit in his tree, not in
> yours yet.

Well, I suspect that David referred to a commit that he just sent by 
email. Which obviously will have a *different* commit ID once you commit 
it - so it probably made sense in his tree, but not once he exported it 
as an email instead of syncing with git natively. 

I also suspect that the whole series was re-ordered in email (or by you 
reading/applying them in a different order). Since now the revert of the 
"disable MSI" happens *before* the patch that looks like it will fix the 
issue.

So I think David also probably didn't number his patches.

			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/