From: Arend van Spriel <arend.vanspriel@broadcom.com>
To: Brian Norris <briannorris@chromium.org>,
Ben Greear <greearb@candelatech.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
Arend van Spriel <aspriel@gmail.com>,
Johannes Berg <johannes.berg@intel.com>
Subject: Re: How to let devcoredump know data has been read?
Date: Wed, 6 Jun 2018 21:08:27 +0200 [thread overview]
Message-ID: <5B18312B.9020208@broadcom.com> (raw)
In-Reply-To: <20180605225324.GA195207@rodete-desktop-imager.corp.google.com>
On 6/6/2018 12:53 AM, Brian Norris wrote:
> Unfortunately, devcoredump is a bit lacking in documentation. Arend was
> writing a bit for the new trigger mechanism at least.
I did indeed write ABI doc for user-space trigger mechanism and you
brought up the need to have ABI doc for devcoredump. I agree it would be
useful and it is dangling at the bottom of my todo list so I did not get
to it (yet). Hopefully I can spend a moment on it.
Regards,
Arend
prev parent reply other threads:[~2018-06-06 19:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-05 22:27 How to let devcoredump know data has been read? Ben Greear
2018-06-05 22:53 ` Brian Norris
2018-06-06 17:04 ` Ben Greear
2018-06-06 19:02 ` Arend van Spriel
2018-06-06 19:08 ` Arend van Spriel [this message]
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=5B18312B.9020208@broadcom.com \
--to=arend.vanspriel@broadcom.com \
--cc=aspriel@gmail.com \
--cc=briannorris@chromium.org \
--cc=greearb@candelatech.com \
--cc=johannes.berg@intel.com \
--cc=linux-wireless@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;
as well as URLs for NNTP newsgroup(s).