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]

Date:	Thu, 3 Jul 2008 12:19:01 -0700
From:	Jesse Barnes <jbarnes@...tuousgeek.org>
To:	Robert Richter <robert.richter@....com>
Cc:	Ingo Molnar <mingo@...e.hu>, Thomas Gleixner <tglx@...utronix.de>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 0/11] x86/pci 32/64 bit merge

On Wednesday, July 02, 2008 1:50 pm Robert Richter wrote:
> This patch series merges the x86/pci code. It's relative to
> tip/x86/cpu since there are already changes that touch pci code.
>
> I reworked parts of the subsys_initcalls to remove Makefile object
> order dependencies. The kernel reboots for acpi/noacpi, smp/nosmp,
> 32/64 bit. It compiles for numaq and visws (I don't have hardware
> available for this configurations, so please test these configs if you
> have hardware available).
>
> There is still some work to do in arch/x86/pci/amd_bus.c and for
> mmconfig.
>
> Signed-off-by: Robert Richter <robert.richter@....com>

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.

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