[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2f0f9522-2d91-4f2f-e4bb-9c63f7676e78@linaro.org>
Date: Sat, 9 Jul 2016 11:00:07 +0800
From: Hanjun Guo <hanjun.guo@...aro.org>
To: "Rafael J. Wysocki" <rjw@...ysocki.net>,
Lorenzo Pieralisi <lorenzo.pieralisi@....com>
Cc: "Rafael J. Wysocki" <rafael@...nel.org>,
Graeme Gregory <gg@...mlogic.co.uk>,
Will Deacon <will.deacon@....com>,
Catalin Marinas <catalin.marinas@....com>,
Fu Wei <fu.wei@...aro.org>, Len Brown <lenb@...nel.org>,
Daniel Lezcano <daniel.lezcano@...aro.org>,
Thomas Gleixner <tglx@...utronix.de>,
Marc Zyngier <marc.zyngier@....com>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"linaro-acpi@...ts.linaro.org" <linaro-acpi@...ts.linaro.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
ACPI Devel Maling List <linux-acpi@...r.kernel.org>,
rruigrok@...eaurora.org, harba@...eaurora.org,
Christopher Covington <cov@...eaurora.org>,
Timur Tabi <timur@...eaurora.org>,
G Gregory <graeme.gregory@...aro.org>,
Al Stone <al.stone@...aro.org>, Jon Masters <jcm@...hat.com>,
wei@...hat.com, Arnd Bergmann <arnd@...db.de>,
Wim Van Sebroeck <wim@...ana.be>,
Suravee Suthikulanit <Suravee.Suthikulpanit@....com>,
Leo Duran <leo.duran@....com>,
Steve Capper <steve.capper@...aro.org>,
Leif Lindholm <leif.lindholm@...aro.org>, sudeep.holla@....com
Subject: Re: [PATCH v6 00/10] acpi, clocksource: add GTDT driver and GTDT
support in arm_arch_timer
On 2016/7/7 21:58, Rafael J. Wysocki wrote:
> On Thursday, July 07, 2016 02:40:23 PM Lorenzo Pieralisi wrote:
>> [+Sudeep]
>>
>> On Thu, Jul 07, 2016 at 02:03:17PM +0200, Rafael J. Wysocki wrote:
>>
>> [...]
>>
>>>>>> So is this a documentation issue in which case Fu Wei can add that to
>>>>>> the file to explain its limited to ARM64. Or we could even rename the
>>>>>> file acpi_arm64_gtdt.c
>>>>>>
>>>>>> It seems a pity as the comment on this series were minors to block
>>>>>> things on a filename/location.
>>>>>
>>>>> Let me repeat what I said above:
>>>>>
>>>>> I'm mostly concerned about how (and by whom) that code is going to be
>>>>> maintained going forward.
>>>>>
>>>>> This is not about documentation, it is about responsibility.
>>>>>
>>>>> Honestly, I don't think I'm the right maintainer to apply the patch
>>>>> introducing this code and then handle bug reports regarding it and so
>>>>> on. That has to be done by somebody else.
>>>>
>>>> I'm working on ACPI for years and upstreamed the ARM64 ACPI core
>>>> support (with lots of people's help), I'm willing to maintain the ARM64
>>>> ACPI code under drivers/acpi/ if no objections.
>>>
>>> OK
>>
>> I would ask you please to add Sudeep and myself for the ARM64 specific
>> ACPI code maintainership too.
>
> OK
>
>>> Can the ARM64-specific code go under drivers/acpi/arm64/ then, for clarity?
I'm fine with it as it helps for maintain.
Thanks
Hanjun
Powered by blists - more mailing lists