Search Linux Wireless

Re: [PATCH 2/4] rfkill: don't restore software blocked state on persistent devices

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, 2009-06-16 at 14:53 +0100, Alan Jenkins wrote:

>  /**
> + * rfkill_init_sw_state - Initialize persistent software block state
> + * @rfkill: pointer to the rfkill class to modify.
> + * @state: the current software block state to set
> + *
> + * rfkill drivers that preserve their software block state over power off
> + * use this function to notify the rfkill core (and through that also
> + * userspace) of their initial state.  It should only be used before
> + * registration.
> + *
> + * In addition, it marks the device as "persistent".  Persistent devices
> + * are expected to preserve preserve their own state when suspended.
> + */
> +void rfkill_init_sw_state(struct rfkill *rfkill, bool blocked);
> +
> +/**
>   * rfkill_set_states - Set the internal rfkill block states
>   * @rfkill: pointer to the rfkill class to modify.
>   * @sw: the current software block state to set

You forgot the inline for !RFKILL.

Otherwise looks good.

johannes

Attachment: signature.asc
Description: This is a digitally signed message part


[Index of Archives]     [Linux Host AP]     [ATH6KL]     [Linux Bluetooth]     [Linux Netdev]     [Kernel Newbies]     [Linux Kernel]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Samba]     [Device Mapper]
  Powered by Linux