From: Arend van Spriel <arend.vanspriel@broadcom.com>
To: Arend van Spriel <aspriel@gmail.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] drivers: base: add description for .coredump() callback
Date: Wed, 14 Mar 2018 10:06:39 +0100 [thread overview]
Message-ID: <5AA8E61F.9090500@broadcom.com> (raw)
In-Reply-To: <1518167637-1948-1-git-send-email-aspriel@gmail.com>
On 2/9/2018 10:13 AM, Arend van Spriel wrote:
> Commit 3c47d19ff4dc ("drivers: base: add coredump driver ops") added
> a new callback in struct device_driver, but not a kerneldoc description
> so here it is.
Hi Greg,
Revisiting the header file I notice this patch is not yet applied. I am
pretty sure I got an automated email from you regarding the merge
window, but nothing else so did this one slip the cracks?
Regards,
Arend
> Fixes: 3c47d19ff4dc ("drivers: base: add coredump driver ops")
> Signed-off-by: Arend van Spriel <aspriel@gmail.com>
> ---
> include/linux/device.h | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/include/linux/device.h b/include/linux/device.h
> index b093405..0b32a42 100644
> --- a/include/linux/device.h
> +++ b/include/linux/device.h
> @@ -256,6 +256,7 @@ enum probe_type {
> * automatically.
> * @pm: Power management operations of the device which matched
> * this driver.
> + * @coredump: Called through sysfs to initiate a device coredump.
> * @p: Driver core's private data, no one other than the driver
> * core can touch this.
> *
>
next prev parent reply other threads:[~2018-03-14 9:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-09 9:13 [PATCH] drivers: base: add description for .coredump() callback Arend van Spriel
2018-03-14 9:06 ` Arend van Spriel [this message]
2018-03-15 9:32 ` Arend van Spriel
2018-03-15 17:27 ` Greg Kroah-Hartman
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=5AA8E61F.9090500@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