On 6 December 2017 at 07:28, Stephen Boyd wrote:
> On 11/21, Chunyan Zhang wrote:
>> On 21 November 2017 at 16:57, Chunyan Zhang wrote:
>> > On 21 November 2017 at 03:12, Stephen Boyd wrote:
>> >> On 11/20, Chunyan Zhang wrote:
On 6 December 2017 at 07:28, Stephen Boyd wrote:
> On 11/21, Chunyan Zhang wrote:
>> On 21 November 2017 at 16:57, Chunyan Zhang wrote:
>> > On 21 November 2017 at 03:12, Stephen Boyd wrote:
>> >> On 11/20, Chunyan Zhang wrote:
>> >>> From: Cai Li
>> >>>
>> >>> In some cases the clock parent
On 11/21, Chunyan Zhang wrote:
> On 21 November 2017 at 16:57, Chunyan Zhang wrote:
> > On 21 November 2017 at 03:12, Stephen Boyd wrote:
> >> On 11/20, Chunyan Zhang wrote:
> >>> From: Cai Li
> >>>
> >>> In some cases the clock
On 11/21, Chunyan Zhang wrote:
> On 21 November 2017 at 16:57, Chunyan Zhang wrote:
> > On 21 November 2017 at 03:12, Stephen Boyd wrote:
> >> On 11/20, Chunyan Zhang wrote:
> >>> From: Cai Li
> >>>
> >>> In some cases the clock parent would be set NULL when doing re-parent,
> >>> it will cause
On 21 November 2017 at 16:57, Chunyan Zhang wrote:
> On 21 November 2017 at 03:12, Stephen Boyd wrote:
>> On 11/20, Chunyan Zhang wrote:
>>> From: Cai Li
>>>
>>> In some cases the clock parent would be set NULL when doing
On 21 November 2017 at 16:57, Chunyan Zhang wrote:
> On 21 November 2017 at 03:12, Stephen Boyd wrote:
>> On 11/20, Chunyan Zhang wrote:
>>> From: Cai Li
>>>
>>> In some cases the clock parent would be set NULL when doing re-parent,
>>> it will cause a NULL pointer accessing if clk_set trace
On 21 November 2017 at 03:12, Stephen Boyd wrote:
> On 11/20, Chunyan Zhang wrote:
>> From: Cai Li
>>
>> In some cases the clock parent would be set NULL when doing re-parent,
>> it will cause a NULL pointer accessing if clk_set trace event is
On 21 November 2017 at 03:12, Stephen Boyd wrote:
> On 11/20, Chunyan Zhang wrote:
>> From: Cai Li
>>
>> In some cases the clock parent would be set NULL when doing re-parent,
>> it will cause a NULL pointer accessing if clk_set trace event is enabled,
>> since the trace event function would not
On 11/20, Chunyan Zhang wrote:
> From: Cai Li
>
> In some cases the clock parent would be set NULL when doing re-parent,
> it will cause a NULL pointer accessing if clk_set trace event is enabled,
> since the trace event function would not check the input parameter.
>
>
On 11/20, Chunyan Zhang wrote:
> From: Cai Li
>
> In some cases the clock parent would be set NULL when doing re-parent,
> it will cause a NULL pointer accessing if clk_set trace event is enabled,
> since the trace event function would not check the input parameter.
>
> Signed-off-by: Cai Li
>
From: Cai Li
In some cases the clock parent would be set NULL when doing re-parent,
it will cause a NULL pointer accessing if clk_set trace event is enabled,
since the trace event function would not check the input parameter.
Signed-off-by: Cai Li
From: Cai Li
In some cases the clock parent would be set NULL when doing re-parent,
it will cause a NULL pointer accessing if clk_set trace event is enabled,
since the trace event function would not check the input parameter.
Signed-off-by: Cai Li
Signed-off-by: Chunyan Zhang
---
12 matches
Mail list logo