Re: [Linaro-acpi] [PATCH v2 0/5] ACPI probing infrastructure

[Al Stone]

On 09/28/2015 07:50 AM, Marc Zyngier wrote:
> On 28/09/15 14:53, Rafael J. Wysocki wrote:
>> On Monday, September 28, 2015 01:59:19 PM Marc Zyngier wrote:
>>> Hi Rafael,
>>>
>>> On 26/09/15 00:45, Rafael J. Wysocki wrote:
>>>
>>>>> Marc Zyngier (5):
>>>>>   acpi: Add basic device probing infrastructure
>>>>>   irqchip/acpi: Add probing infrastructure for ACPI-based irqchips
>>>>>   irqchip/gic: Convert the GIC driver to ACPI probing
>>>>>   clocksource/acpi: Add probing infrastructure for ACPI-based
>>>>>     clocksources
>>>>>   clocksource/arm_arch_timer: Convert to ACPI probing
>>>>
>>>> I'm generally fine with this (modulo a couple of super-minor nits in the
>>>> first patch), but it needs ACKs from Thomas for the irqchip-related and
>>>> clocksource-related patches.
>>>
>>> Sure. I've now addressed your comments, and I'll post the updated series
>>> later today.
>>>
>>>> Plus [3/5] needs to be rebased on top of the Al's patches removing BAD_MADT_ENTRY
>>>> (currently in my bleeding-edge branch).
>>>
>>> Al's patches were there on Friday, but vanished over the weekend. Do you
>>> have another (stable?) branch with these patches in (assuming they are
>>> still aimed at 4.4)?
>>
>> The Al's patches are gone for now, because they introduced a 0-day testing
>> regression.
>>
>> I guess this means I can apply your patches first and ask Al to rebase his
>> next version on them.
> 
> OK. I'll rebase them on the current bleeding-edge, and post that.
> 
> Thanks,
> 
> 	M.
> 

Yeah, sorry about that; I had some bad info from the 1.0 version of the ACPI
spec.  And I was busy with family stuff all weekend.

Rafael, I'll look for Marc's patches to show up in bleeding-edge and rebase on
top of that.

-- 
ciao,
al
-----------------------------------
Al Stone
Software Engineer
Linaro Enterprise Group
al.stone@xxxxxxxxxx
-----------------------------------
--
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/