linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: al.stone@linaro.org (Al Stone)
To: linux-arm-kernel@lists.infradead.org
Subject: [Linaro-acpi] [PATCH v2 0/5] ACPI probing infrastructure
Date: Mon, 28 Sep 2015 13:43:09 -0600	[thread overview]
Message-ID: <5609984D.70702@linaro.org> (raw)
In-Reply-To: <56094589.504@arm.com>

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 at linaro.org
-----------------------------------

  reply	other threads:[~2015-09-28 19:43 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-13 14:02 [PATCH v2 0/5] ACPI probing infrastructure Marc Zyngier
2015-09-13 14:02 ` [PATCH v2 1/5] acpi: Add basic device " Marc Zyngier
2015-09-25 23:54   ` Rafael J. Wysocki
2015-09-13 14:02 ` [PATCH v2 2/5] irqchip/acpi: Add probing infrastructure for ACPI-based irqchips Marc Zyngier
2015-09-13 14:02 ` [PATCH v2 3/5] irqchip/gic: Convert the GIC driver to ACPI probing Marc Zyngier
2015-09-16 15:05   ` Hanjun Guo
2015-09-16 17:28     ` Marc Zyngier
2015-09-16 15:09   ` Hanjun Guo
2015-09-13 14:02 ` [PATCH v2 4/5] clocksource/acpi: Add probing infrastructure for ACPI-based clocksources Marc Zyngier
2015-09-13 14:02 ` [PATCH v2 5/5] clocksource/arm_arch_timer: Convert to ACPI probing Marc Zyngier
2015-09-25 23:45 ` [PATCH v2 0/5] ACPI probing infrastructure Rafael J. Wysocki
2015-09-28 12:59   ` Marc Zyngier
2015-09-28 13:53     ` Rafael J. Wysocki
2015-09-28 13:50       ` Marc Zyngier
2015-09-28 19:43         ` Al Stone [this message]
2015-09-28 19:49           ` [Linaro-acpi] " Rafael J. Wysocki

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5609984D.70702@linaro.org \
    --to=al.stone@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).