linux-kernel - Re: [PATCH 0/11] x86/pci 32/64 bit merge

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: <20080704153904.GB24285@erda.amd.com>
Date:	Fri, 4 Jul 2008 17:39:04 +0200
From:	Robert Richter <robert.richter@....com>
To:	Jesse Barnes <jbarnes@...tuousgeek.org>
CC:	Ingo Molnar <mingo@...e.hu>, Thomas Gleixner <tglx@...utronix.de>,
	LKML <linux-kernel@...r.kernel.org>,
	Yinghai Lu <yhlu.kernel@...il.com>
Subject: Re: [PATCH 0/11] x86/pci 32/64 bit merge

Jesse,

On 03.07.08 12:19:01, Jesse Barnes wrote:
> In general it looks pretty nice and smaller than I would have guessed.  I'd 
> like to see each change have a nicer changelog though, explaining things more 
> than the one line patch summary (why, how, etc.).  And like Yinghai mentioned 
> there may be other changes in the x86 tree that you have to deal with in 
> order to merge this; I can pull those into my PCI linux-next tree though to 
> make things easier.

I will look for changes in other x86 feature trees and cherry-pick all
of them for tip/pci-for-jesse. This will resolve existing conflicts as
well. If the conflicts have small impact, I will create follow on
patches. So, I am fine with applying this patch series to
pci/linux-next.

-Robert

-- 
Advanced Micro Devices, Inc.
Operating System Research Center
email: robert.richter@....com

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