Hi Paul,
It is good for devfreq/devfreq-event framework(patch1/patch2).
But, I think that the device driver (patch3/4/5) should change
the type from 'bool' to 'tristate' instead of using the .
Thanks,
Chanwoo Choi
On 2016년 06월 21일 14:14, Paul Gortmaker wrote:
> For anyone new to the underlying
Hi Paul,
It is good for devfreq/devfreq-event framework(patch1/patch2).
But, I think that the device driver (patch3/4/5) should change
the type from 'bool' to 'tristate' instead of using the .
Thanks,
Chanwoo Choi
On 2016년 06월 21일 14:14, Paul Gortmaker wrote:
> For anyone new to the underlying
For anyone new to the underlying goal of this cleanup, we are trying to
not use module support for code that can never be built as a module since:
(1) it is easy to accidentally write unused module_exit and remove code
(2) it can be misleading when reading the source, thinking it can be
For anyone new to the underlying goal of this cleanup, we are trying to
not use module support for code that can never be built as a module since:
(1) it is easy to accidentally write unused module_exit and remove code
(2) it can be misleading when reading the source, thinking it can be
4 matches
Mail list logo
