On Wed, May 30, 2018 at 12:31 AM, Greg KH wrote:
> On Tue, May 29, 2018 at 11:52:37PM -0700, John Stultz wrote:
>> On Tue, May 29, 2018 at 10:33 PM, Greg KH wrote:
>> > On Tue, May 29, 2018 at 10:14:35PM -0700, John Stultz wrote:
>> >> On Tue, May 8, 2018 at 7:28 PM, Chanwoo Choi
>> >> wrote:
On Wed, May 30, 2018 at 12:31 AM, Greg KH wrote:
> On Tue, May 29, 2018 at 11:52:37PM -0700, John Stultz wrote:
>> On Tue, May 29, 2018 at 10:33 PM, Greg KH wrote:
>> > On Tue, May 29, 2018 at 10:14:35PM -0700, John Stultz wrote:
>> >> On Tue, May 8, 2018 at 7:28 PM, Chanwoo Choi
>> >> wrote:
On Tue, May 29, 2018 at 11:52:37PM -0700, John Stultz wrote:
> On Tue, May 29, 2018 at 10:33 PM, Greg KH wrote:
> > On Tue, May 29, 2018 at 10:14:35PM -0700, John Stultz wrote:
> >> On Tue, May 8, 2018 at 7:28 PM, Chanwoo Choi wrote:
> >> > On 2018년 05월 09일 08:17, John Stultz wrote:
> >> >> Hey
On Tue, May 29, 2018 at 11:52:37PM -0700, John Stultz wrote:
> On Tue, May 29, 2018 at 10:33 PM, Greg KH wrote:
> > On Tue, May 29, 2018 at 10:14:35PM -0700, John Stultz wrote:
> >> On Tue, May 8, 2018 at 7:28 PM, Chanwoo Choi wrote:
> >> > On 2018년 05월 09일 08:17, John Stultz wrote:
> >> >> Hey
On Tue, May 29, 2018 at 10:33 PM, Greg KH wrote:
> On Tue, May 29, 2018 at 10:14:35PM -0700, John Stultz wrote:
>> On Tue, May 8, 2018 at 7:28 PM, Chanwoo Choi wrote:
>> > On 2018년 05월 09일 08:17, John Stultz wrote:
>> >> Hey folks,
>> >> I wanted to bring up an issue we've recently tripped
On Tue, May 29, 2018 at 10:33 PM, Greg KH wrote:
> On Tue, May 29, 2018 at 10:14:35PM -0700, John Stultz wrote:
>> On Tue, May 8, 2018 at 7:28 PM, Chanwoo Choi wrote:
>> > On 2018년 05월 09일 08:17, John Stultz wrote:
>> >> Hey folks,
>> >> I wanted to bring up an issue we've recently tripped
On Tue, May 29, 2018 at 10:14:35PM -0700, John Stultz wrote:
> On Tue, May 8, 2018 at 7:28 PM, Chanwoo Choi wrote:
> > On 2018년 05월 09일 08:17, John Stultz wrote:
> >> Hey folks,
> >> I wanted to bring up an issue we've recently tripped over, which was
> >> caused by 4585fbcb5331f ("PM /
On Tue, May 29, 2018 at 10:14:35PM -0700, John Stultz wrote:
> On Tue, May 8, 2018 at 7:28 PM, Chanwoo Choi wrote:
> > On 2018년 05월 09일 08:17, John Stultz wrote:
> >> Hey folks,
> >> I wanted to bring up an issue we've recently tripped over, which was
> >> caused by 4585fbcb5331f ("PM /
On Tue, May 8, 2018 at 7:28 PM, Chanwoo Choi wrote:
> On 2018년 05월 09일 08:17, John Stultz wrote:
>> Hey folks,
>> I wanted to bring up an issue we've recently tripped over, which was
>> caused by 4585fbcb5331f ("PM / devfreq: Modify the device name as
>> devfreq(X) for sysfs").
>>
>>
On Tue, May 8, 2018 at 7:28 PM, Chanwoo Choi wrote:
> On 2018년 05월 09일 08:17, John Stultz wrote:
>> Hey folks,
>> I wanted to bring up an issue we've recently tripped over, which was
>> caused by 4585fbcb5331f ("PM / devfreq: Modify the device name as
>> devfreq(X) for sysfs").
>>
>>
Hi Chanwoo Choi,
>From my point of view, if it is a new framework, you can use either
the consistent name or device name,
but as a framework has been used for several kernel version, you
should not change the device name
easily if there is no special reason, It will bring no benefits except
for
Hi Chanwoo Choi,
>From my point of view, if it is a new framework, you can use either
the consistent name or device name,
but as a framework has been used for several kernel version, you
should not change the device name
easily if there is no special reason, It will bring no benefits except
for
Hi John,
On 2018년 05월 09일 08:17, John Stultz wrote:
> Hey folks,
> I wanted to bring up an issue we've recently tripped over, which was
> caused by 4585fbcb5331f ("PM / devfreq: Modify the device name as
> devfreq(X) for sysfs").
>
>
Hi John,
On 2018년 05월 09일 08:17, John Stultz wrote:
> Hey folks,
> I wanted to bring up an issue we've recently tripped over, which was
> caused by 4585fbcb5331f ("PM / devfreq: Modify the device name as
> devfreq(X) for sysfs").
>
>
Hey folks,
I wanted to bring up an issue we've recently tripped over, which was
caused by 4585fbcb5331f ("PM / devfreq: Modify the device name as
devfreq(X) for sysfs").
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit?id=4585fbcb5331fc910b7e553ad3efd0dd7b320d14
Hey folks,
I wanted to bring up an issue we've recently tripped over, which was
caused by 4585fbcb5331f ("PM / devfreq: Modify the device name as
devfreq(X) for sysfs").
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit?id=4585fbcb5331fc910b7e553ad3efd0dd7b320d14
16 matches
Mail list logo
