All of lore.kernel.org
 help / color / mirror / Atom feed
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
Date: Tue, 9 Jan 2018 19:46:05 +0100	[thread overview]
Message-ID: <20180109184605.GA28273@kroah.com> (raw)
In-Reply-To: <1513677802-3031-1-git-send-email-arend.vanspriel@broadcom.com>

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

  parent reply	other threads:[~2018-01-09 18:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-19 10:03 [PATCH 0/2] sysfs: allow user-space request for devcoredump Arend van Spriel
2017-12-19 10:03 ` [PATCH 1/2] sysfs: add attribute specification for /sysfs/devices/.../coredump Arend van Spriel
2017-12-19 10:03 ` [PATCH 2/2] drivers: base: add coredump driver ops Arend van Spriel
2018-01-09 18:46 ` Greg Kroah-Hartman [this message]
     [not found]   ` <CAJ65rDyGSirKUqWkXZomMQMA0d=xy=Kc1STzQyKNVymuK_-aMA@mail.gmail.com>
2018-01-09 19:21     ` Fwd: [PATCH 0/2] sysfs: allow user-space request for devcoredump Arend van Spriel
2018-01-09 20:03       ` Greg KH
2018-01-09 20:06         ` Arend van Spriel
2018-01-10  8:22           ` Greg KH

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180109184605.GA28273@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=arend.vanspriel@broadcom.com \
    --cc=aspriel@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.