Catalin, Sudeep,

Hanjun, Al, Graeme and the whole team discuss and review all such patches on the linaro-acpi list before sending them out.

Would it make sense to discuss all these points on such list instead of creating such confusion with the broader linux-acpi or lkml? Even more as Sudeep seems working deeply on ACPI now, it would be very beneficial.

We would welcome all your early comments, as already mentioned months ago.

At Connect we will have ACPI sessions on power management, clocks and regulators and upstreaming.

I expect that by the end of Connect we have a clear well defined list of who you want to ack, who has already ack'ed, who not and why. I also want to agree on who owns ACPI on ARM, as you have raised this question already few times. I do not care who, I care that we do not raise such topics in front of Rafael, as Intel loves just too much to read that the ARM camp is in total confusion.

Thanks
Andrea

On Saturday, February 22, 2014, Catalin Marinas <catalin.marinas@arm.com> wrote:
On 21 Feb 2014, at 23:35, Rafael J. Wysocki <rjw@rjwysocki.net> wrote:
> On Friday, February 21, 2014 06:24:24 PM Catalin Marinas wrote:
>> On Wed, Feb 19, 2014 at 01:50:22AM +0100, Rafael J. Wysocki wrote:
>>> On Wednesday, February 19, 2014 12:23:55 AM Hanjun Guo wrote:
>>>> _PDC related stuff in processor_core.c is little bit X86/IA64 dependent,
>>>> rework the code to make it more arch-independent, no functional change
>>>> in this patch.
>>>>
>>>> Signed-off-by: Hanjun Guo <hanjun.guo@linaro.org>
>>>> Signed-off-by: Graeme Gregory <graeme.gregory@linaro.org>
>>>
>>> I've queued up patches [1,3-5/5] from this series for 3.15 (modulo changelog
>>> modifications), but this one should be CCed to the x86 and ia64 maintainers.
>>
>> Thanks for taking these patches. I would however hold onto patch 3/5 as
>> this is still under discussion. Basically for patches specific to ARM
>> ACPI I would really like to see more acks before being merged as that's
>> a new thing for us.
>
> OK, I'll drop [3/5] for now, then.

Thanks (it’s only temporary ;)).

> I'm wondering, though, whose ACKs I should be waiting for before applying those
> patches?

Good question ;). In this particular case, there is an ongoing
discussion between Hanjun and Sudeep. While there isn’t anything
major, I would like to see some agreement and potentially an Ack from
the other party involved in the discussion (Sudeep).

There are other patches that are not specific to ARM, so it’s
really your decision. As for the general ARM(64) ACPI case, I don’t
think we have anyone in charge with deciding what’s correct or not
(BTW, who are the people active both in the _ARM_ Linux kernel community
and the ACPI standardisation forum?).

In the mean-time, I would like to see at least an ack from the arm-soc
team (Arnd and Olof) or them collecting those ARM-specific patches and
sending pull request to you. My biggest worry is how the ACPI standard
is interpreted by vendors and how (non-standard) features get into the
Linux kernel.

Anyway, I’ll meet the Linaro guys in a week time and we’ll agree on
a way forward.

Thanks,

Catalin
_______________________________________________
Linaro-acpi mailing list
Linaro-acpi@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-acpi


--
Andrea Gallo
Director, Linaro Enterprise Group
email: andrea.gallo@linaro.org
mobile: +39 338 4075993
IRC: agallo@#linaro on irc.linaro.org
Skype: agallo70