Shaun Ruffell 8e2a5def27 hotplug: Do not run auto span configuration if spans are auto assigned. ... This reapplies the change made in commit (6ed0adc08 "dahdi_span_config: Do not run auto span configuration if spans are auto assigned.") which appears to have been accidentally removed in (7f826a7d35 "hotplug modularization: split logic to scriptlets"). To rationale from commit 6ed0adc08: I have seen cases were users run: # modprobe <driver>; dahdi_cfg -c <custom config file> and the spans end up misconfigured because dahdi_span_assignments ends up running, via udev, after the user configured the span the way it wanted. dahdi_span_assignments now looks at auto_assign_spans module parameter on dahdi.ko, like dahdi_handle_device already does, to determine if legacy or udev based configuration is being done. Signed-off-by: Shaun Ruffell <sruffell@digium.com>		2014-01-31 11:16:08 -06:00
..
handle_device.d	hotplug modularization: split logic to scriptlets	2014-01-23 12:35:59 +02:00
span_config.d	hotplug: document asterisk scriptlet	2014-01-28 11:32:31 +02:00
dahdi_handle_device	hotplug modularization: split logic to scriptlets	2014-01-23 12:35:59 +02:00
dahdi_span_config	hotplug: Do not run auto span configuration if spans are auto assigned.	2014-01-31 11:16:08 -06:00