From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mark Brown Subject: Re: [PATCH v7 00/17] Introduce ACPI for ARM64 based on ACPI 5.1 Date: Thu, 15 Jan 2015 19:02:20 +0000 Message-ID: <20150115190220.GF3043@sirena.org.uk> References: <1421247905-3749-1-git-send-email-hanjun.guo@linaro.org> <20150115182346.GE2329@e104818-lin.cambridge.arm.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="NG5rUlMnWRrIcOiS" Return-path: Received: from mezzanine.sirena.org.uk ([106.187.55.193]:34820 "EHLO mezzanine.sirena.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751240AbbAOTDy (ORCPT ); Thu, 15 Jan 2015 14:03:54 -0500 Content-Disposition: inline In-Reply-To: <20150115182346.GE2329@e104818-lin.cambridge.arm.com> Sender: linux-acpi-owner@vger.kernel.org List-Id: linux-acpi@vger.kernel.org To: Catalin Marinas Cc: Grant Likely , Will Deacon , "hanjun.guo@linaro.org" , "Rafael J. Wysocki" , Olof Johansson , Arnd Bergmann , Mark Rutland , Lorenzo Pieralisi , "graeme.gregory@linaro.org" , Sudeep Holla , "jcm@redhat.com" , Jason Cooper , Marc Zyngier , Bjorn Helgaas , Rob Herring , Robert Richter , Randy Dunlap , Charles Garcia-Tobin , "phoenix.liyi@huawei.com" , Timur Tabi , "suravee.suthikulpanit@amd.com" Yijing Wang --NG5rUlMnWRrIcOiS Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Thu, Jan 15, 2015 at 06:23:47PM +0000, Catalin Marinas wrote: > On Thu, Jan 15, 2015 at 04:26:20PM +0000, Grant Likely wrote: > > I'll get right to the point: Can we please have this series queued up > > for v3.20? > Before you even ask for this, please look at the patches and realise > that there is a complete lack of Reviewed-by tags on the code (well, > apart from trivial Kconfig changes). In addition, the series touches on > other subsystems like clocksource, irqchip, acpi and I don't see any > acks from the corresponding maintainers. So even if I wanted to merge > the series, there is no way it can be done without additional > reviews/acks. On the document (last patch), I'd like to see a statement There's probably a bit of a process problem here - these patches are all being posted as part of big and apparently controversial threads with subject lines in the form "ARM / ACPI:" so people could be forgiven for just not even reading the e-mails enough to notice changes to their subsystems. Is it worth posting those patches separately more directly to the relevant maintainers? --NG5rUlMnWRrIcOiS Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJUuA67AAoJECTWi3JdVIfQPRkH/1ijhO5P9oVbefqwA7XIM/1e ZtsyeEY0FD4aZGA98Z6GqpdQlKP5fAb+m66zOtoHDuZvyVkvriAWgLYvNpOBb5Rm unWsQ2NzBoF2C2H4GsOECM1492Xq0cEWK8l5QfQTed+scK8Tgj+yKc1qQONK1dbU pHochHpEq/HJnBLiiXviGVO1pCrpGzGC74GFYqi4OLuhd2Ke9deMqM4BEXgH1SFj JgIv2TuPrDGMNGG6FEww0VPERONsVkMg8clTdqdvTpMLz31z+Bl1Wd8jOO7z7PsE te05HzOrz18rsop7JpbxJ2ac2gYAE1diIiEnyh9ypXpyXdbvw2L/StqjkPr1WrI= =THbv -----END PGP SIGNATURE----- --NG5rUlMnWRrIcOiS-- From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753452AbbAOTD5 (ORCPT ); Thu, 15 Jan 2015 14:03:57 -0500 Received: from mezzanine.sirena.org.uk ([106.187.55.193]:34820 "EHLO mezzanine.sirena.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751240AbbAOTDy (ORCPT ); Thu, 15 Jan 2015 14:03:54 -0500 Date: Thu, 15 Jan 2015 19:02:20 +0000 From: Mark Brown To: Catalin Marinas Cc: Grant Likely , Will Deacon , "hanjun.guo@linaro.org" , "Rafael J. Wysocki" , Olof Johansson , Arnd Bergmann , Mark Rutland , Lorenzo Pieralisi , "graeme.gregory@linaro.org" , Sudeep Holla , "jcm@redhat.com" , Jason Cooper , Marc Zyngier , Bjorn Helgaas , Rob Herring , Robert Richter , Randy Dunlap , Charles Garcia-Tobin , "phoenix.liyi@huawei.com" , Timur Tabi , "suravee.suthikulpanit@amd.com" , Yijing Wang , ACPI Devel Mailing List , "linux-arm-kernel@lists.infradead.org" , Linux Kernel Mailing List , linaro-acpi Message-ID: <20150115190220.GF3043@sirena.org.uk> References: <1421247905-3749-1-git-send-email-hanjun.guo@linaro.org> <20150115182346.GE2329@e104818-lin.cambridge.arm.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="NG5rUlMnWRrIcOiS" Content-Disposition: inline In-Reply-To: <20150115182346.GE2329@e104818-lin.cambridge.arm.com> X-Cookie: To program is to be. User-Agent: Mutt/1.5.23 (2014-03-12) X-SA-Exim-Connect-IP: 94.175.94.161 X-SA-Exim-Mail-From: broonie@sirena.org.uk Subject: Re: [PATCH v7 00/17] Introduce ACPI for ARM64 based on ACPI 5.1 X-SA-Exim-Version: 4.2.1 (built Mon, 26 Dec 2011 16:24:06 +0000) X-SA-Exim-Scanned: Yes (on mezzanine.sirena.org.uk) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org --NG5rUlMnWRrIcOiS Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Thu, Jan 15, 2015 at 06:23:47PM +0000, Catalin Marinas wrote: > On Thu, Jan 15, 2015 at 04:26:20PM +0000, Grant Likely wrote: > > I'll get right to the point: Can we please have this series queued up > > for v3.20? > Before you even ask for this, please look at the patches and realise > that there is a complete lack of Reviewed-by tags on the code (well, > apart from trivial Kconfig changes). In addition, the series touches on > other subsystems like clocksource, irqchip, acpi and I don't see any > acks from the corresponding maintainers. So even if I wanted to merge > the series, there is no way it can be done without additional > reviews/acks. On the document (last patch), I'd like to see a statement There's probably a bit of a process problem here - these patches are all being posted as part of big and apparently controversial threads with subject lines in the form "ARM / ACPI:" so people could be forgiven for just not even reading the e-mails enough to notice changes to their subsystems. Is it worth posting those patches separately more directly to the relevant maintainers? --NG5rUlMnWRrIcOiS Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJUuA67AAoJECTWi3JdVIfQPRkH/1ijhO5P9oVbefqwA7XIM/1e ZtsyeEY0FD4aZGA98Z6GqpdQlKP5fAb+m66zOtoHDuZvyVkvriAWgLYvNpOBb5Rm unWsQ2NzBoF2C2H4GsOECM1492Xq0cEWK8l5QfQTed+scK8Tgj+yKc1qQONK1dbU pHochHpEq/HJnBLiiXviGVO1pCrpGzGC74GFYqi4OLuhd2Ke9deMqM4BEXgH1SFj JgIv2TuPrDGMNGG6FEww0VPERONsVkMg8clTdqdvTpMLz31z+Bl1Wd8jOO7z7PsE te05HzOrz18rsop7JpbxJ2ac2gYAE1diIiEnyh9ypXpyXdbvw2L/StqjkPr1WrI= =THbv -----END PGP SIGNATURE----- --NG5rUlMnWRrIcOiS-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: broonie@kernel.org (Mark Brown) Date: Thu, 15 Jan 2015 19:02:20 +0000 Subject: [PATCH v7 00/17] Introduce ACPI for ARM64 based on ACPI 5.1 In-Reply-To: <20150115182346.GE2329@e104818-lin.cambridge.arm.com> References: <1421247905-3749-1-git-send-email-hanjun.guo@linaro.org> <20150115182346.GE2329@e104818-lin.cambridge.arm.com> Message-ID: <20150115190220.GF3043@sirena.org.uk> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On Thu, Jan 15, 2015 at 06:23:47PM +0000, Catalin Marinas wrote: > On Thu, Jan 15, 2015 at 04:26:20PM +0000, Grant Likely wrote: > > I'll get right to the point: Can we please have this series queued up > > for v3.20? > Before you even ask for this, please look at the patches and realise > that there is a complete lack of Reviewed-by tags on the code (well, > apart from trivial Kconfig changes). In addition, the series touches on > other subsystems like clocksource, irqchip, acpi and I don't see any > acks from the corresponding maintainers. So even if I wanted to merge > the series, there is no way it can be done without additional > reviews/acks. On the document (last patch), I'd like to see a statement There's probably a bit of a process problem here - these patches are all being posted as part of big and apparently controversial threads with subject lines in the form "ARM / ACPI:" so people could be forgiven for just not even reading the e-mails enough to notice changes to their subsystems. Is it worth posting those patches separately more directly to the relevant maintainers? -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 473 bytes Desc: Digital signature URL: