Re: [PATCH 1/4] PM / devfreq: Track overall load monitor state instead of 'stop_polling'

Hi Matthias, On 19. 2. 15. 오전 1:59, Matthias Kaehlcke wrote: > Hi Chanwoo, > > On Thu, Feb 14, 2019 at 11:25:52PM +0900, Chanwoo Choi wrote: >> Hi Matthias, >> >> 2019년 2월 14일 (목) 오후 7:16, Matthias Kaehlcke 님이 작성: >>> >>> The field ->stop_polling indicates whether load monitoring should be/is

Re: [PATCH 1/4] PM / devfreq: Track overall load monitor state instead of 'stop_polling'

Hi Chanwoo, On Thu, Feb 14, 2019 at 11:25:52PM +0900, Chanwoo Choi wrote: > Hi Matthias, > > 2019년 2월 14일 (목) 오후 7:16, Matthias Kaehlcke 님이 작성: > > > > The field ->stop_polling indicates whether load monitoring should be/is > > stopped, it is set in devfreq_monitor_suspend(). Change the variable

Re: [PATCH 1/4] PM / devfreq: Track overall load monitor state instead of 'stop_polling'

Hi Matthias, 2019년 2월 14일 (목) 오후 7:16, Matthias Kaehlcke 님이 작성: > > The field ->stop_polling indicates whether load monitoring should be/is > stopped, it is set in devfreq_monitor_suspend(). Change the variable to > hold the general state of load monitoring (stopped, running, suspended). >

[PATCH 1/4] PM / devfreq: Track overall load monitor state instead of 'stop_polling'

The field ->stop_polling indicates whether load monitoring should be/is stopped, it is set in devfreq_monitor_suspend(). Change the variable to hold the general state of load monitoring (stopped, running, suspended). Besides improving readability of conditions involving the field and this prepares