From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1753880AbcESHxH (ORCPT <rfc822;w@1wt.eu>);
	Thu, 19 May 2016 03:53:07 -0400
Received: from mout.gmx.net ([212.227.15.18]:54076 "EHLO mout.gmx.net"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1751362AbcESHxF (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
	Thu, 19 May 2016 03:53:05 -0400
Subject: Re: [PATCH] Input: pwm-beeper - fix: scheduling while atomic
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
References: <56C4735E.6020300@gmx.at> <20160222194639.GD26177@dtor-ws>
 <20160512121852.GB26824@ulmo.ba.sec> <5735F4E3.20008@gmx.at>
 <573C8761.9070601@gmx.at> <20160518160601.GB5407@kroah.com>
Cc: Thierry Reding <thierry.reding@gmail.com>,
        Dmitry Torokhov <dmitry.torokhov@gmail.com>,
        Manfred Schlaegl <manfred.schlaegl@ginzinger.com>,
        Luis de Bethencourt <luis@debethencourt.com>,
        Olivier Sobrie <olivier@sobrie.be>, linux-input@vger.kernel.org,
        linux-kernel@vger.kernel.org
From: Manfred Schlaegl <manfred.schlaegl@gmx.at>
X-Enigmail-Draft-Status: N1110
Message-ID: <573D70D5.7070401@gmx.at>
Date: Thu, 19 May 2016 09:52:53 +0200
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:38.0) Gecko/20100101
 Icedove/38.8.0
MIME-Version: 1.0
In-Reply-To: <20160518160601.GB5407@kroah.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
X-Provags-ID: V03:K0:Zvn8z5l+yBTopZIm/PSa3lH035MipzXS54y2cZzvWfl1szW5pnH
 pP6guM7BkJOsQ4wUTkBeHRISCGLTmXk1q0BWmOjAJy6rysTGfxrMTHOrJiaEMBKm/PtDW6T
 nsQk7qtERSc0maBIleUH15x995EGWpfwVlYYwL75vsj/p0rWgxpi62NqQ9S2vUXURHaqAqn
 7Gz6nt3bj27zVtJZH8jVw==
X-UI-Out-Filterresults: notjunk:1;V01:K0:rCi7b+6Xp/c=:+XHjaH/oY0uEylLTeS8L8v
 krRFzvoi2cDXrxYMeHNvhZwTiafIjVOJVAfbk44iZ14dFduI+1VxSta21z3M2cRFwgvm4plXw
 SjEciK4eAnPXBBes7F4cZ11cd5pCB3mInVqQsZK9eyrCwQXYsPFACRwotU1lAlhSdHCa7NwHy
 oOd198Wth/6Beyh8i7pkle7VO5vBu+LF0CO9z29W8Gbgv6IBe+b2z+gV0rzFJQ2iJ0WoXzlhI
 IgmiF3sYR9pha0XZndKbYM1DI8z1dqgdQ8I83Vnbr8zCzJnARCTZU3XEL5ocltz0jJLr42065
 1hAl33BOP7/KIGeJUqdclBQBahRJMGhC3SiK5/0t9hGxMc1tWa98CDKzXEb5IS0OFmj9W0soD
 bNTCsNRrK3pekPe1ZlaJrj/IRZ2l1htLuhPIyE+FFrU3+z/iN3xX8iepbPBEYTbbZ1XuveMMm
 o5QDV6wZzV2L2rV2vHV28JJkEQ6N/p+l72PzmQgbDAXla2nafBxQw5FlwvAe156xeHP4aw2HJ
 YPxT4T1iMkdci7k9J1rQMylnKjpKbUHPzoXUlF0Ff8ocNDZj/cuLIHg3dPFKVmshwrNEXb6LN
 4rJl7zF8M7ogSDwhJ1awcn4uwKxinSgjNQHZ9NklHI02LRA5/5CiUcvfCMs95OBy2J9gy36HF
 YGXcl4xeQSgpOb9gJqU7yUNu3Tfc+zSv9+ZKYJdEHb42u0H97DNt988ypcFN91SKZFEf+puNy
 ngtNmWYPxftjFma5pa6jblEpOhjXLEkphmEadL0kT9m+JQcRjjhrMgZLDU8w3vbeUYsgJH/nW
 dZu8p8o
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

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