linux-kernel - Re: [Patch v3 0/4] Introduce a mechanism to allocate PCI IRQ on demand

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: <559CD763.50601@linux.intel.com>
Date:	Wed, 08 Jul 2015 15:55:15 +0800
From:	Jiang Liu <jiang.liu@...ux.intel.com>
To:	Thomas Gleixner <tglx@...utronix.de>
CC:	Bjorn Helgaas <bhelgaas@...gle.com>,
	"Rafael J . Wysocki" <rjw@...ysocki.net>,
	LKML <linux-kernel@...r.kernel.org>, linux-pci@...r.kernel.org,
	linux-acpi@...r.kernel.org, "x86 @ kernel . org" <x86@...nel.org>
Subject: Re: [Patch v3 0/4] Introduce a mechanism to allocate PCI IRQ on demand

On 2015/7/8 15:40, Thomas Gleixner wrote:
> On Wed, 8 Jul 2015, Jiang Liu wrote:
>> On 2015/6/20 0:10, Bjorn Helgaas wrote:
>>> On Wed, Jun 10, 2015 at 04:54:57PM +0800, Jiang Liu wrote:
>>>> Hi Bjorn,
>>>> 	I have verified that this patch set could be applied to the
>>>> mainstream kernel without dependency on other patches, so could you
>>>> please help to merge it?
>>>
>>> I already acked these and said I was willing to merge them and that I was
>>> hoping for an ack from Thomas.
>>>
>>> Any thoughts, Thomas?
>>
>> Hi Thomas,
>> 	Any comments about this bugfix series?
> 
> How is these a bugfix series? It looks like preparation for ioapic
> hotplug.
> 
> But other than that, Acked-by-me.
Thanks! The IOAPIC hotplug driver has been merged into mainstream
kernel, so treat them as bugfix:)
--
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/