Alan Jenkins wrote: > rfkill_set_global_sw_state() (previously rfkill_set_default()) will no > longer be exported by the rewritten rfkill core. > > Instead, platform drivers which can provide persistent soft-rfkill state > across power-down/reboot should indicate their initial state by calling > rfkill_set_sw_state() before registration. Otherwise, they will be > initialized to a default value during registration by a set_block call. > > We remove existing calls to rfkill_set_sw_state() which happen before > registration, since these had no effect in the old model. If these > drivers do have persistent state, the calls can be put back (subject > to testing :-). This affects hp-wmi and acer-wmi. > > > Drivers with persistent state will affect the global state only if > rfkill-input is enabled. This is required, otherwise booting with > wireless soft-blocked and pressing the wireless-toggle key once would > have no apparent effect. This special case will be removed in future > along with rfkill-input, in favour of a more flexible userspace daemon > (see Documentation/feature-removal-schedule.txt). > > > Now rfkill_global_states[n].def is only used to preserve global states > over EPO, it is renamed to ".sav". > > Signed-off-by: Alan Jenkins <alan-jenkins@xxxxxxxxxxxxxx> > --- > v2: > - fix thinkpad-acpi message to reflect altered error-case behaviour > - remove !CONFIG_RFKILL stub for rfkill_set_global_sw_state() > Sorry, wrong patch, try again -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
