Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753957AbbLJVnV (ORCPT ); Thu, 10 Dec 2015 16:43:21 -0500 Received: from mail-vk0-f41.google.com ([209.85.213.41]:33702 "EHLO mail-vk0-f41.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753843AbbLJVnS (ORCPT ); Thu, 10 Dec 2015 16:43:18 -0500 MIME-Version: 1.0 In-Reply-To: References: <1449610162-30543-1-git-send-email-john.stultz@linaro.org> <10759786.VG6jMebqAj@wuerfel> <1721197.gFcIQMjGvs@wuerfel> Date: Thu, 10 Dec 2015 13:43:16 -0800 Message-ID: Subject: Re: [RFC][PATCH] misc: Introduce reboot_reason driver From: John Stultz To: Rob Herring Cc: Arnd Bergmann , Bjorn Andersson , lkml , Pawel Moll , Mark Rutland , Ian Campbell , Kumar Gala , Vinay Simha BN , Haojian Zhuang , "devicetree@vger.kernel.org" , Android Kernel Team , Andy Gross , "linux-arm-msm@vger.kernel.org" Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 828 Lines: 20 On Thu, Dec 10, 2015 at 12:24 PM, Rob Herring wrote: > The fact that we are using notifiers for reset reason and triggering > is probably some indication that some infrastructure is needed. But I > don't think you need to do that here as long as it is all kernel > internals. We'll make the 2nd guy do it. ;) :) Though, just so I understand better, what is problematic w/ the reset notifiers? They provide the reboot command argument, which is the core of what is needed. It actually seemed like it was almost designed with this problem in mind. thanks -john -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/