All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hanjun Guo <hanjun.guo@linaro.org>
To: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
	"Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: "Rafael J. Wysocki" <rafael@kernel.org>,
	Graeme Gregory <gg@slimlogic.co.uk>,
	Will Deacon <will.deacon@arm.com>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Fu Wei <fu.wei@linaro.org>, Len Brown <lenb@kernel.org>,
	Daniel Lezcano <daniel.lezcano@linaro.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Marc Zyngier <marc.zyngier@arm.com>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"linaro-acpi@lists.linaro.org" <linaro-acpi@lists.linaro.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
	rruigrok@codeaurora.org, harba@codeaurora.org,
	Christopher Covington <cov@codeaurora.org>,
	Timur Tabi <timur@codeaurora.org>,
	G Gregory <graeme.gregory@linaro.org>,
	Al Stone <al.stone@linaro.org>, Jon Masters <jcm@redhat.com>,
	wei@redhat.com, Arnd Bergmann <arnd@arndb.de>,
	Wim
Subject: Re: [PATCH v6 00/10] acpi, clocksource: add GTDT driver and GTDT support in arm_arch_timer
Date: Sat, 9 Jul 2016 11:44:47 +0800	[thread overview]
Message-ID: <21ec2b0d-cde9-f86a-c39a-0fba5d02fd03@linaro.org> (raw)
In-Reply-To: <20160708132201.GD3784@red-moon>

On 2016/7/8 21:22, Lorenzo Pieralisi wrote:
> On Thu, Jul 07, 2016 at 03:58:04PM +0200, Rafael J. Wysocki wrote:
>
> [...]
>
>>> Anyway let's avoid these petty arguments, I agree there must be some
>>> sort of ARM64 ACPI maintainership for the reasons you mentioned above.
>>
>> To avoid confusion on who's going to push stuff to Linus, I can do
>> that, but it must be clear whose ACKs are needed for that to happen.
>> That may be one person or all of you, whatever you decide.
>
> I think the reasoning is the same, to avoid confusion and avoid stepping
> on each other toes it is best to have a single gatekeeper (still
> multiple maintainer entries to keep patches reviewed correctly), if no
> one complains I will do that and a) provide ACKs (I will definitely
> require and request Hanjun and Sudeep ones too appropriately on a per
> patch basis) and b) send you pull requests.

Fine to me.

>
> Having a maintainer per file would be farcical, I really do not

Agree, but having three of us in maintainer entries in MAINTAINERS
file will help the patches be reviewed correctly with more eyes.

> expect that amount of traffic for drivers/acpi/arm64 therefore I
> really doubt there is any risk of me slowing things down.
>
> Does this sound reasonable ? Comments/complaints welcome, please
> manifest yourselves.

Fair enough. What I'm concern most is land ACPI on ARM64 soundly,
let's do that :)

OK, let's back to this patch set, Fuwei already prepared a new version
of patches [1] (moving acpi_gtdt.c to drivers/acpi/arm64/ and add a
maintainer entries patch), shall we review and comment on this patch
set for now, or just let Fuwei send out the new version?

[1]: 
https://git.linaro.org/people/fu.wei/linux.git/shortlog/refs/heads/topic-gtdt-wakeup-timer_upstream_v7_devel

Thanks
Hanjun

WARNING: multiple messages have this Message-ID (diff)
From: Hanjun Guo <hanjun.guo@linaro.org>
To: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
	"Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: "Rafael J. Wysocki" <rafael@kernel.org>,
	Graeme Gregory <gg@slimlogic.co.uk>,
	Will Deacon <will.deacon@arm.com>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Fu Wei <fu.wei@linaro.org>, Len Brown <lenb@kernel.org>,
	Daniel Lezcano <daniel.lezcano@linaro.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Marc Zyngier <marc.zyngier@arm.com>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
	"linaro-acpi@lists.linaro.org" <linaro-acpi@lists.linaro.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
	rruigrok@codeaurora.org, harba@codeaurora.org,
	Christopher Covington <cov@codeaurora.org>,
	Timur Tabi <timur@codeaurora.org>,
	G Gregory <graeme.gregory@linaro.org>,
	Al Stone <al.stone@linaro.org>, Jon Masters <jcm@redhat.com>,
	wei@redhat.com, Arnd Bergmann <arnd@arndb.de>,
	Wim Van Sebroeck <wim@iguana.be>,
	Suravee Suthikulanit <Suravee.Suthikulpanit@amd.com>,
	Leo Duran <leo.duran@amd.com>,
	Steve Capper <steve.capper@linaro.org>,
	Leif Lindholm <leif.lindholm@linaro.org>,
	sudeep.holla@arm.com
Subject: Re: [PATCH v6 00/10] acpi, clocksource: add GTDT driver and GTDT support in arm_arch_timer
Date: Sat, 9 Jul 2016 11:44:47 +0800	[thread overview]
Message-ID: <21ec2b0d-cde9-f86a-c39a-0fba5d02fd03@linaro.org> (raw)
In-Reply-To: <20160708132201.GD3784@red-moon>

On 2016/7/8 21:22, Lorenzo Pieralisi wrote:
> On Thu, Jul 07, 2016 at 03:58:04PM +0200, Rafael J. Wysocki wrote:
>
> [...]
>
>>> Anyway let's avoid these petty arguments, I agree there must be some
>>> sort of ARM64 ACPI maintainership for the reasons you mentioned above.
>>
>> To avoid confusion on who's going to push stuff to Linus, I can do
>> that, but it must be clear whose ACKs are needed for that to happen.
>> That may be one person or all of you, whatever you decide.
>
> I think the reasoning is the same, to avoid confusion and avoid stepping
> on each other toes it is best to have a single gatekeeper (still
> multiple maintainer entries to keep patches reviewed correctly), if no
> one complains I will do that and a) provide ACKs (I will definitely
> require and request Hanjun and Sudeep ones too appropriately on a per
> patch basis) and b) send you pull requests.

Fine to me.

>
> Having a maintainer per file would be farcical, I really do not

Agree, but having three of us in maintainer entries in MAINTAINERS
file will help the patches be reviewed correctly with more eyes.

> expect that amount of traffic for drivers/acpi/arm64 therefore I
> really doubt there is any risk of me slowing things down.
>
> Does this sound reasonable ? Comments/complaints welcome, please
> manifest yourselves.

Fair enough. What I'm concern most is land ACPI on ARM64 soundly,
let's do that :)

OK, let's back to this patch set, Fuwei already prepared a new version
of patches [1] (moving acpi_gtdt.c to drivers/acpi/arm64/ and add a
maintainer entries patch), shall we review and comment on this patch
set for now, or just let Fuwei send out the new version?

[1]: 
https://git.linaro.org/people/fu.wei/linux.git/shortlog/refs/heads/topic-gtdt-wakeup-timer_upstream_v7_devel

Thanks
Hanjun

WARNING: multiple messages have this Message-ID (diff)
From: hanjun.guo@linaro.org (Hanjun Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v6 00/10] acpi, clocksource: add GTDT driver and GTDT support in arm_arch_timer
Date: Sat, 9 Jul 2016 11:44:47 +0800	[thread overview]
Message-ID: <21ec2b0d-cde9-f86a-c39a-0fba5d02fd03@linaro.org> (raw)
In-Reply-To: <20160708132201.GD3784@red-moon>

On 2016/7/8 21:22, Lorenzo Pieralisi wrote:
> On Thu, Jul 07, 2016 at 03:58:04PM +0200, Rafael J. Wysocki wrote:
>
> [...]
>
>>> Anyway let's avoid these petty arguments, I agree there must be some
>>> sort of ARM64 ACPI maintainership for the reasons you mentioned above.
>>
>> To avoid confusion on who's going to push stuff to Linus, I can do
>> that, but it must be clear whose ACKs are needed for that to happen.
>> That may be one person or all of you, whatever you decide.
>
> I think the reasoning is the same, to avoid confusion and avoid stepping
> on each other toes it is best to have a single gatekeeper (still
> multiple maintainer entries to keep patches reviewed correctly), if no
> one complains I will do that and a) provide ACKs (I will definitely
> require and request Hanjun and Sudeep ones too appropriately on a per
> patch basis) and b) send you pull requests.

Fine to me.

>
> Having a maintainer per file would be farcical, I really do not

Agree, but having three of us in maintainer entries in MAINTAINERS
file will help the patches be reviewed correctly with more eyes.

> expect that amount of traffic for drivers/acpi/arm64 therefore I
> really doubt there is any risk of me slowing things down.
>
> Does this sound reasonable ? Comments/complaints welcome, please
> manifest yourselves.

Fair enough. What I'm concern most is land ACPI on ARM64 soundly,
let's do that :)

OK, let's back to this patch set, Fuwei already prepared a new version
of patches [1] (moving acpi_gtdt.c to drivers/acpi/arm64/ and add a
maintainer entries patch), shall we review and comment on this patch
set for now, or just let Fuwei send out the new version?

[1]: 
https://git.linaro.org/people/fu.wei/linux.git/shortlog/refs/heads/topic-gtdt-wakeup-timer_upstream_v7_devel

Thanks
Hanjun

  parent reply	other threads:[~2016-07-09  3:45 UTC|newest]

Thread overview: 124+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-29 18:15 [PATCH v6 00/10] acpi, clocksource: add GTDT driver and GTDT support in arm_arch_timer fu.wei
2016-06-29 18:15 ` fu.wei at linaro.org
2016-06-29 18:15 ` fu.wei
2016-06-29 18:15 ` [PATCH v6 01/10] clocksource/drivers/arm_arch_timer: Move enums and defines to header file fu.wei
2016-06-29 18:15   ` fu.wei at linaro.org
2016-06-29 18:15   ` fu.wei
2016-06-29 18:15 ` [PATCH v6 02/10] clocksource/drivers/arm_arch_timer: Add a new enum for spi type fu.wei
2016-06-29 18:15   ` fu.wei at linaro.org
2016-06-29 18:15   ` fu.wei
2016-06-29 18:15 ` [PATCH v6 03/10] clocksource/drivers/arm_arch_timer: Improve printk relevant code fu.wei
2016-06-29 18:15   ` fu.wei at linaro.org
2016-06-30  2:54   ` Hanjun Guo
2016-06-30  2:54     ` Hanjun Guo
2016-07-07 16:12     ` Fu Wei
2016-07-07 16:12       ` Fu Wei
2016-06-29 18:15 ` [PATCH v6 04/10] acpi: Add some basic struct and functions in GTDT driver fu.wei
2016-06-29 18:15   ` fu.wei at linaro.org
2016-06-29 21:24   ` Rafael J. Wysocki
2016-06-29 21:24     ` Rafael J. Wysocki
2016-06-29 21:24     ` Rafael J. Wysocki
2016-06-30  1:17     ` Fu Wei
2016-06-30  1:17       ` Fu Wei
2016-06-30  1:17       ` Fu Wei
2016-06-30  1:26       ` Rafael J. Wysocki
2016-06-30  1:26         ` Rafael J. Wysocki
2016-06-30  1:26         ` Rafael J. Wysocki
2016-06-30  1:32         ` Fu Wei
2016-06-30  1:32           ` Fu Wei
2016-06-30  1:32           ` Fu Wei
2016-06-30  4:13         ` Timur Tabi
2016-06-30  4:13           ` Timur Tabi
2016-06-30  4:13           ` Timur Tabi
2016-06-29 18:15 ` [PATCH v6 05/10] acpi: Add arch_timer support in GTDT table parse driver fu.wei
2016-06-29 18:15   ` fu.wei at linaro.org
2016-06-29 18:15   ` fu.wei
2016-06-29 18:15 ` [PATCH v6 06/10] acpi: Add GTDT driver to kernel build system fu.wei
2016-06-29 18:15   ` fu.wei at linaro.org
2016-06-29 18:15   ` fu.wei
2016-06-29 18:15 ` [PATCH v6 07/10] clocksource/drivers/arm_arch_timer: Simplify ACPI support code fu.wei
2016-06-29 18:15   ` fu.wei at linaro.org
2016-06-29 18:15 ` [PATCH v6 08/10] acpi: Add memory-mapped timer support in GTDT driver fu.wei
2016-06-29 18:15   ` fu.wei at linaro.org
2016-06-29 18:15   ` fu.wei
2016-06-29 18:15 ` [PATCH v6 09/10] clocksource/drivers/arm_arch_timer: Add GTDT support for memory-mapped timer fu.wei
2016-06-29 18:15   ` fu.wei at linaro.org
2016-06-29 18:15   ` fu.wei
2016-06-29 18:15 ` [PATCH v6 10/10] acpi: Add SBSA Generic Watchdog support in GTDT driver fu.wei
2016-06-29 18:15   ` fu.wei at linaro.org
2016-06-29 18:15   ` fu.wei
2016-06-29 21:32 ` [PATCH v6 00/10] acpi, clocksource: add GTDT driver and GTDT support in arm_arch_timer Rafael J. Wysocki
2016-06-29 21:32   ` Rafael J. Wysocki
2016-06-29 21:32   ` Rafael J. Wysocki
2016-06-30  1:29   ` Fu Wei
2016-06-30  1:29     ` Fu Wei
2016-06-30  1:29     ` Fu Wei
2016-06-30  1:37     ` Rafael J. Wysocki
2016-06-30  1:37       ` Rafael J. Wysocki
2016-06-30  1:37       ` Rafael J. Wysocki
2016-06-30  2:10       ` Hanjun Guo
2016-06-30  2:10         ` Hanjun Guo
2016-06-30  2:10         ` Hanjun Guo
2016-06-30 13:27         ` Rafael J. Wysocki
2016-06-30 13:27           ` Rafael J. Wysocki
2016-06-30 13:27           ` Rafael J. Wysocki
2016-06-30 13:48           ` Hanjun Guo
2016-06-30 13:48             ` Hanjun Guo
2016-06-30 13:48             ` Hanjun Guo
2016-07-01 15:23             ` Will Deacon
2016-07-01 15:23               ` Will Deacon
2016-07-01 15:23               ` Will Deacon
2016-07-01 21:04               ` Rafael J. Wysocki
2016-07-01 21:04                 ` Rafael J. Wysocki
2016-07-01 21:04                 ` Rafael J. Wysocki
2016-07-04 12:53                 ` Rafael J. Wysocki
2016-07-04 12:53                   ` Rafael J. Wysocki
2016-07-04 12:53                   ` Rafael J. Wysocki
2016-07-05 14:18                   ` Graeme Gregory
2016-07-05 14:18                     ` Graeme Gregory
2016-07-05 14:18                     ` Graeme Gregory
2016-07-06  0:00                     ` Rafael J. Wysocki
2016-07-06  0:00                       ` Rafael J. Wysocki
2016-07-06  0:00                       ` Rafael J. Wysocki
2016-07-07 11:12                       ` Hanjun Guo
2016-07-07 11:12                         ` Hanjun Guo
2016-07-07 11:12                         ` Hanjun Guo
2016-07-07 12:03                         ` Rafael J. Wysocki
2016-07-07 12:03                           ` Rafael J. Wysocki
2016-07-07 12:03                           ` Rafael J. Wysocki
2016-07-07 13:40                           ` Lorenzo Pieralisi
2016-07-07 13:40                             ` Lorenzo Pieralisi
2016-07-07 13:40                             ` Lorenzo Pieralisi
2016-07-07 13:58                             ` Rafael J. Wysocki
2016-07-07 13:58                               ` Rafael J. Wysocki
2016-07-07 13:58                               ` Rafael J. Wysocki
2016-07-07 15:21                               ` Fu Wei
2016-07-07 15:21                                 ` Fu Wei
2016-07-07 15:21                                 ` Fu Wei
2016-07-08 13:22                               ` Lorenzo Pieralisi
2016-07-08 13:22                                 ` Lorenzo Pieralisi
2016-07-08 13:22                                 ` Lorenzo Pieralisi
2016-07-08 13:50                                 ` Sudeep Holla
2016-07-08 13:50                                   ` Sudeep Holla
2016-07-08 13:50                                   ` Sudeep Holla
2016-07-09  3:44                                 ` Hanjun Guo [this message]
2016-07-09  3:44                                   ` Hanjun Guo
2016-07-09  3:44                                   ` Hanjun Guo
2016-07-10  1:26                                   ` Rafael J. Wysocki
2016-07-10  1:26                                     ` Rafael J. Wysocki
2016-07-10  1:26                                     ` Rafael J. Wysocki
2016-07-09  3:00                               ` Hanjun Guo
2016-07-09  3:00                                 ` Hanjun Guo
2016-07-09  3:00                                 ` Hanjun Guo
2016-07-01 14:00           ` Daniel Lezcano
2016-07-01 14:00             ` Daniel Lezcano
2016-07-01 14:00             ` Daniel Lezcano
2016-07-01 21:01             ` Rafael J. Wysocki
2016-07-01 21:01               ` Rafael J. Wysocki
2016-07-01 21:01               ` Rafael J. Wysocki
2016-07-04 13:43               ` Daniel Lezcano
2016-07-04 13:43                 ` Daniel Lezcano
2016-07-04 13:43                 ` Daniel Lezcano
2016-07-04 14:19                 ` Rafael J. Wysocki
2016-07-04 14:19                   ` Rafael J. Wysocki
2016-07-04 14:19                   ` 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=21ec2b0d-cde9-f86a-c39a-0fba5d02fd03@linaro.org \
    --to=hanjun.guo@linaro.org \
    --cc=al.stone@linaro.org \
    --cc=arnd@arndb.de \
    --cc=catalin.marinas@arm.com \
    --cc=cov@codeaurora.org \
    --cc=daniel.lezcano@linaro.org \
    --cc=fu.wei@linaro.org \
    --cc=gg@slimlogic.co.uk \
    --cc=graeme.gregory@linaro.org \
    --cc=harba@codeaurora.org \
    --cc=jcm@redhat.com \
    --cc=lenb@kernel.org \
    --cc=linaro-acpi@lists.linaro.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lorenzo.pieralisi@arm.com \
    --cc=marc.zyngier@arm.com \
    --cc=rafael@kernel.org \
    --cc=rjw@rjwysocki.net \
    --cc=rruigrok@codeaurora.org \
    --cc=tglx@linutronix.de \
    --cc=timur@codeaurora.org \
    --cc=wei@redhat.com \
    --cc=will.deacon@arm.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.