On 01/07/2019 23:43, Martin Blumenstingl wrote:
> On Fri, Jun 28, 2019 at 6:05 PM Martin Blumenstingl
> wrote:
>>
>> Hi Colin,
>>
>> On Fri, Jun 28, 2019 at 10:32 AM Colin Ian King
>> wrote:
>>>
>>> On 28/06/2019 05:15, Martin Blumenstingl wrote:
On Tue, Jun 25, 2019 at 9:58 AM Colin Ian Kin
On Fri, Jun 28, 2019 at 6:05 PM Martin Blumenstingl
wrote:
>
> Hi Colin,
>
> On Fri, Jun 28, 2019 at 10:32 AM Colin Ian King
> wrote:
> >
> > On 28/06/2019 05:15, Martin Blumenstingl wrote:
> > > On Tue, Jun 25, 2019 at 9:58 AM Colin Ian King
> > > wrote:
> > >>
> > >> On 25/06/2019 05:44, Mart
Hi Colin,
On Fri, Jun 28, 2019 at 10:32 AM Colin Ian King
wrote:
>
> On 28/06/2019 05:15, Martin Blumenstingl wrote:
> > On Tue, Jun 25, 2019 at 9:58 AM Colin Ian King
> > wrote:
> >>
> >> On 25/06/2019 05:44, Martin Blumenstingl wrote:
> >>> Hi Colin,
> >>>
> >>> On Thu, Jun 20, 2019 at 3:34 A
On 28/06/2019 05:15, Martin Blumenstingl wrote:
> On Tue, Jun 25, 2019 at 9:58 AM Colin Ian King
> wrote:
>>
>> On 25/06/2019 05:44, Martin Blumenstingl wrote:
>>> Hi Colin,
>>>
>>> On Thu, Jun 20, 2019 at 3:34 AM Martin Blumenstingl
>>> wrote:
Hi Colin,
On Wed, Jun 19, 2019
On Tue, Jun 25, 2019 at 9:58 AM Colin Ian King wrote:
>
> On 25/06/2019 05:44, Martin Blumenstingl wrote:
> > Hi Colin,
> >
> > On Thu, Jun 20, 2019 at 3:34 AM Martin Blumenstingl
> > wrote:
> >>
> >> Hi Colin,
> >>
> >> On Wed, Jun 19, 2019 at 8:55 AM Colin Ian King
> >> wrote:
> >>>
> >>> On
On 25/06/2019 05:44, Martin Blumenstingl wrote:
> Hi Colin,
>
> On Thu, Jun 20, 2019 at 3:34 AM Martin Blumenstingl
> wrote:
>>
>> Hi Colin,
>>
>> On Wed, Jun 19, 2019 at 8:55 AM Colin Ian King
>> wrote:
>>>
>>> On 19/06/2019 06:13, Martin Blumenstingl wrote:
Hi Colin,
> Currently
Hi Colin,
On Thu, Jun 20, 2019 at 3:34 AM Martin Blumenstingl
wrote:
>
> Hi Colin,
>
> On Wed, Jun 19, 2019 at 8:55 AM Colin Ian King
> wrote:
> >
> > On 19/06/2019 06:13, Martin Blumenstingl wrote:
> > > Hi Colin,
> > >
> > >> Currently the call to device_property_read_u32_array is not error c
Hi Colin,
On Wed, Jun 19, 2019 at 8:55 AM Colin Ian King wrote:
>
> On 19/06/2019 06:13, Martin Blumenstingl wrote:
> > Hi Colin,
> >
> >> Currently the call to device_property_read_u32_array is not error checked
> >> leading to potential garbage values in the delays array that are then used
> >>
On 19/06/2019 06:13, Martin Blumenstingl wrote:
> Hi Colin,
>
>> Currently the call to device_property_read_u32_array is not error checked
>> leading to potential garbage values in the delays array that are then used
>> in msleep delays. Add a sanity check to the property fetching.
>>
>> Addresse
Hi Colin,
> Currently the call to device_property_read_u32_array is not error checked
> leading to potential garbage values in the delays array that are then used
> in msleep delays. Add a sanity check to the property fetching.
>
> Addresses-Coverity: ("Uninitialized scalar variable")
> Signed-o
From: Colin King
Date: Mon, 17 Jun 2019 17:58:36 +0100
> From: Colin Ian King
>
> Currently the call to device_property_read_u32_array is not error checked
> leading to potential garbage values in the delays array that are then used
> in msleep delays. Add a sanity check to the property fetchi
From: Colin Ian King
Currently the call to device_property_read_u32_array is not error checked
leading to potential garbage values in the delays array that are then used
in msleep delays. Add a sanity check to the property fetching.
Addresses-Coverity: ("Uninitialized scalar variable")
Signed-o
12 matches
Mail list logo