2018-02-09 09:17:16

by Arend Van Spriel

[permalink] [raw]
Subject: [PATCH] drivers: base: add description for .coredump() callback

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.

Fixes: 3c47d19ff4dc ("drivers: base: add coredump driver ops")
Signed-off-by: Arend van Spriel <[email protected]>
---
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.
*
--
1.9.1



2018-03-14 09:08:04

by Arend Van Spriel

[permalink] [raw]
Subject: Re: [PATCH] drivers: base: add description for .coredump() callback

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 <[email protected]>
> ---
> 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.
> *
>


2018-03-15 09:33:57

by Arend Van Spriel

[permalink] [raw]
Subject: Re: [PATCH] drivers: base: add description for .coredump() callback

On 3/14/2018 10:06 AM, Arend van Spriel wrote:
> 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?

Hi Greg,

As I am touching this in follow-up patch, can we just drop this one? I
will be posting a couple of new patch assuming it is fine to drop this.
Let me know how you want to handle this.

Regards,
Arend

> Regards,
> Arend
>
>> Fixes: 3c47d19ff4dc ("drivers: base: add coredump driver ops")
>> Signed-off-by: Arend van Spriel <[email protected]>
>> ---
>> 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.
>> *
>>
>


2018-03-15 17:29:18

by Greg Kroah-Hartman

[permalink] [raw]
Subject: Re: [PATCH] drivers: base: add description for .coredump() callback

On Thu, Mar 15, 2018 at 10:32:53AM +0100, Arend van Spriel wrote:
> On 3/14/2018 10:06 AM, Arend van Spriel wrote:
> > 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?
>
> Hi Greg,
>
> As I am touching this in follow-up patch, can we just drop this one? I will
> be posting a couple of new patch assuming it is fine to drop this. Let me
> know how you want to handle this.

Just applied this, it's trivial and should be simple to merge around.

thanks,

greg k-h