Hi Krzysztof,
On 11 May 2016 at 11:19, Krzysztof Kozlowski wrote:
> On 05/10/2016 09:45 PM, Anand Moon wrote:
>> Hi Krzysztof,
>>
>> Sorry I am not able to explain my self clearly.
>> But I have once gain tested these changes.
>>
>> Only could you append with following
Hi Krzysztof,
On 11 May 2016 at 11:19, Krzysztof Kozlowski wrote:
> On 05/10/2016 09:45 PM, Anand Moon wrote:
>> Hi Krzysztof,
>>
>> Sorry I am not able to explain my self clearly.
>> But I have once gain tested these changes.
>>
>> Only could you append with following changes.
>>
On 05/10/2016 09:45 PM, Anand Moon wrote:
> Hi Krzysztof,
>
> Sorry I am not able to explain my self clearly.
> But I have once gain tested these changes.
>
> Only could you append with following changes.
>
> +
On 05/10/2016 09:45 PM, Anand Moon wrote:
> Hi Krzysztof,
>
> Sorry I am not able to explain my self clearly.
> But I have once gain tested these changes.
>
> Only could you append with following changes.
>
> +
Hi Krzysztof,
On 10 May 2016 at 19:33, Krzysztof Kozlowski wrote:
> On 05/10/2016 04:00 PM, Anand Moon wrote:
>> Hi Krzysztof,
>>
>> On 10 May 2016 at 18:13, Krzysztof Kozlowski wrote:
>>> On 05/10/2016 11:29 AM, Anand Moon wrote:
>
> I
Hi Krzysztof,
On 10 May 2016 at 19:33, Krzysztof Kozlowski wrote:
> On 05/10/2016 04:00 PM, Anand Moon wrote:
>> Hi Krzysztof,
>>
>> On 10 May 2016 at 18:13, Krzysztof Kozlowski wrote:
>>> On 05/10/2016 11:29 AM, Anand Moon wrote:
>
> I am sorry but I do not understand.
> 1. Are you
On 05/10/2016 04:00 PM, Anand Moon wrote:
> Hi Krzysztof,
>
> On 10 May 2016 at 18:13, Krzysztof Kozlowski wrote:
>> On 05/10/2016 11:29 AM, Anand Moon wrote:
I am sorry but I do not understand.
1. Are you saying that my patch causes the issue?
2. Are
On 05/10/2016 04:00 PM, Anand Moon wrote:
> Hi Krzysztof,
>
> On 10 May 2016 at 18:13, Krzysztof Kozlowski wrote:
>> On 05/10/2016 11:29 AM, Anand Moon wrote:
I am sorry but I do not understand.
1. Are you saying that my patch causes the issue?
2. Are you saying that I should
Hi Krzysztof,
On 10 May 2016 at 18:13, Krzysztof Kozlowski wrote:
> On 05/10/2016 11:29 AM, Anand Moon wrote:
>>>
>>> I am sorry but I do not understand.
>>> 1. Are you saying that my patch causes the issue?
>>> 2. Are you saying that I should not send some patches
Hi Krzysztof,
On 10 May 2016 at 18:13, Krzysztof Kozlowski wrote:
> On 05/10/2016 11:29 AM, Anand Moon wrote:
>>>
>>> I am sorry but I do not understand.
>>> 1. Are you saying that my patch causes the issue?
>>> 2. Are you saying that I should not send some patches because of
>>> conflicting
On 05/10/2016 11:29 AM, Anand Moon wrote:
>>
>> I am sorry but I do not understand.
>> 1. Are you saying that my patch causes the issue?
>> 2. Are you saying that I should not send some patches because of
>> conflicting work? (that would be peculiar...)
>> 3. Are you saying that I should not apply
On 05/10/2016 11:29 AM, Anand Moon wrote:
>>
>> I am sorry but I do not understand.
>> 1. Are you saying that my patch causes the issue?
>> 2. Are you saying that I should not send some patches because of
>> conflicting work? (that would be peculiar...)
>> 3. Are you saying that I should not apply
Hi Krzysztof,
On 10 May 2016 at 13:45, Krzysztof Kozlowski wrote:
> On 05/10/2016 08:43 AM, Anand Moon wrote:
>> Hi Krzysztof ,
>>
>> On 9 May 2016 at 11:49, Krzysztof Kozlowski wrote:
>>> Include the CPU thermal nodes directly in Odroid
Hi Krzysztof,
On 10 May 2016 at 13:45, Krzysztof Kozlowski wrote:
> On 05/10/2016 08:43 AM, Anand Moon wrote:
>> Hi Krzysztof ,
>>
>> On 9 May 2016 at 11:49, Krzysztof Kozlowski wrote:
>>> Include the CPU thermal nodes directly in Odroid XU3-family common DTS
>>> because it is the only user of
On 05/10/2016 08:43 AM, Anand Moon wrote:
> Hi Krzysztof ,
>
> On 9 May 2016 at 11:49, Krzysztof Kozlowski wrote:
>> Include the CPU thermal nodes directly in Odroid XU3-family common DTS
>> because it is the only user of it. Keeping it in separate DTSI node does
>> not
On 05/10/2016 08:43 AM, Anand Moon wrote:
> Hi Krzysztof ,
>
> On 9 May 2016 at 11:49, Krzysztof Kozlowski wrote:
>> Include the CPU thermal nodes directly in Odroid XU3-family common DTS
>> because it is the only user of it. Keeping it in separate DTSI node does
>> not bring benefits because:
Hi Krzysztof ,
On 9 May 2016 at 11:49, Krzysztof Kozlowski wrote:
> Include the CPU thermal nodes directly in Odroid XU3-family common DTS
> because it is the only user of it. Keeping it in separate DTSI node does
> not bring benefits because:
> 1. It is not re-usable on
Hi Krzysztof ,
On 9 May 2016 at 11:49, Krzysztof Kozlowski wrote:
> Include the CPU thermal nodes directly in Odroid XU3-family common DTS
> because it is the only user of it. Keeping it in separate DTSI node does
> not bring benefits because:
> 1. It is not re-usable on other non-fan boards
Hello Krzysztof,
On 05/09/2016 02:19 AM, Krzysztof Kozlowski wrote:
> Include the CPU thermal nodes directly in Odroid XU3-family common DTS
> because it is the only user of it. Keeping it in separate DTSI node does
> not bring benefits because:
> 1. It is not re-usable on other non-fan boards
Hello Krzysztof,
On 05/09/2016 02:19 AM, Krzysztof Kozlowski wrote:
> Include the CPU thermal nodes directly in Odroid XU3-family common DTS
> because it is the only user of it. Keeping it in separate DTSI node does
> not bring benefits because:
> 1. It is not re-usable on other non-fan boards
Include the CPU thermal nodes directly in Odroid XU3-family common DTS
because it is the only user of it. Keeping it in separate DTSI node does
not bring benefits because:
1. It is not re-usable on other non-fan boards (fan is referenced),
2. It won't be re-used on future Odroid XU board because
Include the CPU thermal nodes directly in Odroid XU3-family common DTS
because it is the only user of it. Keeping it in separate DTSI node does
not bring benefits because:
1. It is not re-usable on other non-fan boards (fan is referenced),
2. It won't be re-used on future Odroid XU board because
22 matches
Mail list logo