mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Arend van Spriel <arend.vanspriel@broadcom.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org, Arend van Spriel <aspriel@gmail.com>
Subject: [PATCH 0/2] sysfs: allow user-space request for devcoredump
Date: Tue, 19 Dec 2017 11:03:20 +0100	[thread overview]
Message-ID: <1513677802-3031-1-git-send-email-arend.vanspriel@broadcom.com> (raw)

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.

These patches apply to the driver-core-next branch of the driver-core
repository.

Arend van Spriel (2):
  sysfs: add attribute specification for /sysfs/devices/.../coredump
  drivers: base: add coredump driver ops

 Documentation/ABI/testing/sysfs-devices-coredump | 10 ++++++
 drivers/base/dd.c                                | 40 +++++++++++++++++++-----
 include/linux/device.h                           |  2 +-
 3 files changed, 44 insertions(+), 8 deletions(-)
 create mode 100644 Documentation/ABI/testing/sysfs-devices-coredump

-- 
1.9.1

             reply	other threads:[~2017-12-19 10:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-19 10:03 Arend van Spriel [this message]
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 ` [PATCH 0/2] sysfs: allow user-space request for devcoredump Greg Kroah-Hartman
     [not found]   ` <CAJ65rDyGSirKUqWkXZomMQMA0d=xy=Kc1STzQyKNVymuK_-aMA@mail.gmail.com>
2018-01-09 19:21     ` Fwd: " 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=1513677802-3031-1-git-send-email-arend.vanspriel@broadcom.com \
    --to=arend.vanspriel@broadcom.com \
    --cc=aspriel@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®