Hi,
On 27.05.2020 15:05, Matthias Brugger wrote:
On 27/05/2020 08:41, Ovidiu Panait wrote:
According to the description of devfdt_get_addr_ptr, this function should
return NULL on failure, but currently it returns (void *)FDT_ADDR_T_NONE.
This is also a problem because there are two
Hi Sean,
On Thu, 28 May 2020 at 13:29, Sean Anderson wrote:
>
> On 5/28/20 10:32 AM, Simon Glass wrote:
> > On Wed, 27 May 2020 at 00:45, Ovidiu Panait
> > wrote:
> >>
> >> According to the description of devfdt_get_addr_ptr, this function should
> >> return NULL on failure, but currently it
On 5/28/20 10:32 AM, Simon Glass wrote:
> On Wed, 27 May 2020 at 00:45, Ovidiu Panait
> wrote:
>>
>> According to the description of devfdt_get_addr_ptr, this function should
>> return NULL on failure, but currently it returns (void *)FDT_ADDR_T_NONE.
>>
>> This is also a problem because there
On Wed, 27 May 2020 at 00:45, Ovidiu Panait wrote:
>
> According to the description of devfdt_get_addr_ptr, this function should
> return NULL on failure, but currently it returns (void *)FDT_ADDR_T_NONE.
>
> This is also a problem because there are two definitions for
> dev_read_addr_ptr,
On 5/27/20 8:41 AM, Ovidiu Panait wrote:
> According to the description of devfdt_get_addr_ptr, this function
> should return NULL on failure, but currently it returns (void
> *)FDT_ADDR_T_NONE.
>
> This is also a problem because there are two definitions for
> dev_read_addr_ptr, depending on
On 27/05/2020 08:41, Ovidiu Panait wrote:
> According to the description of devfdt_get_addr_ptr, this function should
> return NULL on failure, but currently it returns (void *)FDT_ADDR_T_NONE.
>
> This is also a problem because there are two definitions for
> dev_read_addr_ptr, depending on
6 matches
Mail list logo