Hi,
Le Tue, 23 Jan 2018 11:24:05 +0100,
Greg Kroah-Hartman a écrit :
> Instead of "open coding" a DEVICE_ATTR() define, use the
> DEVICE_ATTR_RW() macro instead, which does everything properly instead.
>
> This does require a few static functions to be renamed to work properly,
> but thanks to
On Tue, Jan 23, 2018 at 11:24:05AM +0100, Greg Kroah-Hartman wrote:
> Instead of "open coding" a DEVICE_ATTR() define, use the
> DEVICE_ATTR_RW() macro instead, which does everything properly instead.
>
> This does require a few static functions to be renamed to work properly,
> but thanks to a sc
On Tue, 23 Jan 2018, Greg Kroah-Hartman wrote:
> Instead of "open coding" a DEVICE_ATTR() define, use the
> DEVICE_ATTR_RW() macro instead, which does everything properly instead.
>
> This does require a few static functions to be renamed to work properly,
> but thanks to a script from Joe Perche
On Tue, Jan 23, 2018 at 12:26:38PM +0200, Felipe Balbi wrote:
>
> Hi,
>
> Greg Kroah-Hartman writes:
> > Instead of "open coding" a DEVICE_ATTR() define, use the
> > DEVICE_ATTR_RW() macro instead, which does everything properly instead.
> >
> > This does require a few static functions to be ren
Hi,
Greg Kroah-Hartman writes:
> Instead of "open coding" a DEVICE_ATTR() define, use the
> DEVICE_ATTR_RW() macro instead, which does everything properly instead.
>
> This does require a few static functions to be renamed to work properly,
> but thanks to a script from Joe Perches, this was eas
