Re: [PATCH 00/19 v3] Improve IRQ remapping abstraction in x86 corecode

From: Sebastian Andrzej Siewior
Date: Thu Nov 01 2012 - 17:37:22 EST


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On Wed, Sep 26, 2012 at 12:44:32PM +0200, Joerg Roedel wrote:
> Hi,
Hi JÃrg,

> here is the third version of the patch-set to improve the abstraction
> of interrupt remapping in the x86 core code. A more detailed description

I went through the whole series and looks good. The patches
- - x86, io_apic: Introduce x86_io_apic_ops.disable()
- - x86, io_apic: Introduce x86_io_apic_ops.print_entries for debugging
- - x86, msi: Use IRQ remapping specific setup_msi_irqs routine
- - x86, io_apic: Convert setup_ioapic_entry to function pointerx86, io_apic:
- - x86, io_apic: Move irq_remapping_enabled checks out of check_timer()
- - x86, io-apic: Move CONFIG_IRQ_REMAP code out of x86 core

trigger some checkpatch warnings, mostly the 80char thingy. I don't care about
the "quoted string split across lines" warning.
Besides the minor thingy I just mentioned,
Acked-by: Sebastian Andrzej Siewior <sebastian@xxxxxxxxxxxxx>

Sebastian
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQIcBAEBCAAGBQJQkuuWAAoJEHuW6BYqjPXRnVwP/08DxdazUY4SOPIvBK4+gZh7
3VW5EdTLjBSYnaWEFccwhaqqq6FgJ5MfJ862sSXUpejjApDFQdOQPlZmIwfY5lFh
n3z20/6Nvum6mCvZLUEi7D+cQZ42ZWfyQW62dBxwQvw6sex884f5DUFqftlCUJzA
qlCBXoqVRkW03stfH8j4rDI+lponuR6P1m7hdV4r7CB95RthME/ZOpHQ3G2qSTRF
7mCRJ6eP7eLdZSichWHuhyXcil1uADglPw8m9PKtEE7AW9satiXO/b/pEFiDDdNr
xcb7Sc3OalccYVe7/Hs5WypNg05e/N4WHuTx4Y4gD2f6pHJA64bbZ6+3nmMJBt9y
NbCzuDg1dgXFG0YQkPCbULGSnu/Z6DKnryrPvmRhCQUS7w8pXMOfhdKz8q2v+l8G
riej/ZGHCGbf0UmvM+HguTjuTTCGMdvkCRGpx/UwVvy8Ll5sb0o73ORw25hdPHdD
VGaximc4jmRBTSMB7ncOCMYOjTp6CKhG2ZvtA6q+JDS+GGTv3tfEBHri2STzZ7BY
SrG8boABWJq39xxsivltimMJFa9IBCWpTyb/yG7T4I4ypOwI2QSdRob/Rs/BprHI
SdzYlj2BFiR3ToF8WDXrMw9ywkVG6QL1oVrUDA+LHaBZO574KW/LMMuktYCj+gmY
mQEcW6k8kS39uBtiL0Kh
=tIW6
-----END PGP SIGNATURE-----
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/