Shipping this in linux-restricted modules-2.6.x-y would mean either file conflicts, or a versioned conffile name for each kernel revision. Shipping it in linux-restricted-modules-common will make it tricky to roll this back, if and when the module no longer has to be reloaded on suspend/resume. Under the circumstances, would it not be simpler to ship this setting in pm-utils itself?
Shipping this in linux-restricted modules-2.6.x-y would mean either file conflicts, or a versioned conffile name for each kernel revision. Shipping it in linux-restricte d-modules- common will make it tricky to roll this back, if and when the module no longer has to be reloaded on suspend/resume. Under the circumstances, would it not be simpler to ship this setting in pm-utils itself?