Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751670AbeABHT5 (ORCPT + 1 other); Tue, 2 Jan 2018 02:19:57 -0500 Received: from mail-qt0-f196.google.com ([209.85.216.196]:33504 "EHLO mail-qt0-f196.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751521AbeABHTz (ORCPT ); Tue, 2 Jan 2018 02:19:55 -0500 X-Google-Smtp-Source: ACJfBou4TCsms4zMleOxZqJ1Ik29nlhqmhwDWtBHHs2trYaLBrnA+45XENoC/lbyHcfCbOCjP8usp1/nLkdcBD/TVL0= MIME-Version: 1.0 In-Reply-To: References: From: Amit Kucheria Date: Tue, 2 Jan 2018 12:49:54 +0530 Message-ID: Subject: Re: [PATCH v2 0/4] arm64: defconfig: enable additional led triggers To: Arnd Bergmann 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 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? Thanks for applying the patches. Wish you a Happy New Year. Regards, Amit