Date: Tue, 9 Jan 2018 19:46:05 +0100
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Arend van Spriel <arend.vanspriel@broadcom.com>
Cc: linux-kernel@vger.kernel.org, Arend van Spriel <aspriel@gmail.com>
Subject: Re: [PATCH 0/2] sysfs: allow user-space request for devcoredump
Message-ID: <20180109184605.GA28273@kroah.com>
References: <1513677802-3031-1-git-send-email-arend.vanspriel@broadcom.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1513677802-3031-1-git-send-email-arend.vanspriel@broadcom.com>
User-Agent: Mutt/1.9.2 (2017-12-15)
Sender: linux-kernel-owner@vger.kernel.org

On Tue, Dec 19, 2017 at 11:03:20AM +0100, Arend van Spriel wrote:
> From: Arend van Spriel <aspriel@gmail.com>
> 
> Since commit 833c95456a70 ("device coredump: add new device coredump class")
> device drivers have a unified way to provide binary data obtained from a
> failing_device to user-space. However, there may be use-cases in which the
> driver has no reason to obtain the data, but user-space wants to initiate
> it. This adds a coredump device attribute in sysfs when the driver bound to
> the device supports the newly added coredump driver callback.

What driver is going to set this?  I don't want to add new options to
the kernel that never get used, do you have a driver to use it?

thanks,

greg k-h