Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753573AbeADQyR (ORCPT + 1 other); Thu, 4 Jan 2018 11:54:17 -0500 Received: from mail-ot0-f194.google.com ([74.125.82.194]:40537 "EHLO mail-ot0-f194.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752684AbeADQyO (ORCPT ); Thu, 4 Jan 2018 11:54:14 -0500 X-Google-Smtp-Source: ACJfBou9FIdwufU5/o+ELouR5lvRJ5hX3vdS5MhhgIT/95jjWGglKs8MaEuIMnRDx1JAhF5k+x51S7nkg3civanp4I4= MIME-Version: 1.0 In-Reply-To: References: From: Arnd Bergmann Date: Thu, 4 Jan 2018 17:54:13 +0100 X-Google-Sender-Auth: uYjIkwapsmuO_1V9fCglkJbulzU Message-ID: Subject: Re: [PATCH v2 0/4] arm64: defconfig: enable additional led triggers To: Amit Kucheria Cc: LKML , Andy Gross , linux-arm-msm@vger.kernel.org, lakml , Wei Xu , Manivannan Sadhasivam , DTML , Timur Tabi Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Return-Path: On Tue, Jan 2, 2018 at 8:19 AM, Amit Kucheria wrote: > On Thu, Dec 21, 2017 at 8:46 PM, Arnd Bergmann wrote: >> On Wed, Dec 6, 2017 at 9:57 AM, Amit Kucheria wrote: >>> (Adding Arnd) >>> >>> Now that the merge window rush has abated, can you please apply this >>> trivial series? >>> >>> On Mon, Nov 6, 2017 at 12:38 PM, Amit Kucheria wrote: >>>> This patchset enables the kernel panic and disk-activity trigger for LEDs >>>> and then enables the panic trigger for three 96Boards - DB410c, Hikey and >>>> Hikey960. >>>> >>>> DB410c and Hikey panic behaviour has been tested by triggering a panic >>>> through /proc/sysrq-trigger, while Hikey960 is only compile-tested. >> >> I applied all four now, but it would have been easier for me if you had either >> sent them to the platform maintainers, or to arm@kernel.org. > > The platform maintainers are cc'ed but I guess nobody took them since > the patchset touched 3 different platforms and a common defconfig. > > I'll remember to cc arm@kernel.org in the future but is there any > reason why this email address isn't listed in MAINTAINERS? We normally want to have all patches merged through the platform maintainers, and have no ambiguity regarding who picks things up. More importantly, being listed in the MAINTAINERS file would result in us getting thousands of patches each merge window mixed in with the stuff that we actually do need to see, so that would likely be more lossy and more work for us. Arnd