On 03/12/2017 01:21 PM, Simon Glass wrote:
> Hi York,
>
> On 3 March 2017 at 09:38, york sun wrote:
>>
>> On 03/02/2017 08:53 PM, Simon Glass wrote:
>>> Hi York,
>>>
>>> On 1 March 2017 at 12:32, York Sun wrote:
Use gd->arch.resv_ram to track reserved
Hi York,
On 3 March 2017 at 09:38, york sun wrote:
>
> On 03/02/2017 08:53 PM, Simon Glass wrote:
> > Hi York,
> >
> > On 1 March 2017 at 12:32, York Sun wrote:
> >> Use gd->arch.resv_ram to track reserved memory allocation.
> >>
> >> Signed-off-by: York Sun
On 03/02/2017 08:53 PM, Simon Glass wrote:
> Hi York,
>
> On 1 March 2017 at 12:32, York Sun wrote:
>> Use gd->arch.resv_ram to track reserved memory allocation.
>>
>> Signed-off-by: York Sun
>> ---
>>
>> Changes in v3: None
>> Changes in v2: None
>>
>>
Hi York,
On 1 March 2017 at 12:32, York Sun wrote:
> Use gd->arch.resv_ram to track reserved memory allocation.
>
> Signed-off-by: York Sun
> ---
>
> Changes in v3: None
> Changes in v2: None
>
> arch/arm/cpu/armv8/fsl-layerscape/Kconfig | 6 ++
>
Use gd->arch.resv_ram to track reserved memory allocation.
Signed-off-by: York Sun
---
Changes in v3: None
Changes in v2: None
arch/arm/cpu/armv8/fsl-layerscape/Kconfig | 6 ++
arch/arm/include/asm/global_data.h| 3 +++
cmd/bdinfo.c |
5 matches
Mail list logo