On 2016-05-18 18:06, Greg Kroah-Hartman wrote: > On Wed, May 18, 2016 at 05:16:49PM +0200, Manfred Schlaegl wrote: >> Pwm config may sleep so defer it using a worker. >> >> Trigger: >> On a Freescale i.MX53 based board we ran into "BUG: scheduling while >> atomic" because input_inject_event locks interrupts, but >> imx_pwm_config_v2 sleeps. >> >> Tested on Freescale i.MX53 SoC with 4.6.0 and 4.1.24. >> >> Unmodified applicable to >> * 4.6 (stable) >> * 4.5.4 (stable) >> * 4.4.10 (longterm) >> * 4.1.24 (longterm) >> >> Modified applicable to >> * 3.18.33 (longterm) > > What does this all mean? Have you read > Documentation/stable_kernel_rules.txt for how to mark things for stable > inclusion? > > thanks, > > greg k-h > Sorry, I'm afraid I missed that. Thanks for the clarification. I will respect that in the future. Should I resend the patch with a cleaned up message (without "Unmodified applicable to" and "Modified applicable to" stuff)? Is the rest of message (formally) ok? thanks, manfred -- To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
