On 10/14/21 13:17, Adrian Fiergolski wrote:
On 14.10.2021 11:47, Michal Simek wrote:
On 10/14/21 10:54, Adrian Fiergolski wrote:
On 14.10.2021 at 09:22, Michal Simek wrote:
First of all subject is quite long. Please make it shorter and remove
dot at the end.
On 10/13/21 18:21, Adrian
On 14.10.2021 11:47, Michal Simek wrote:
>
>
> On 10/14/21 10:54, Adrian Fiergolski wrote:
>> On 14.10.2021 at 09:22, Michal Simek wrote:
>>>
>>> First of all subject is quite long. Please make it shorter and remove
>>> dot at the end.
>>>
>>>
>>> On 10/13/21 18:21, Adrian Fiergolski wrote:
On 10/14/21 10:54, Adrian Fiergolski wrote:
On 14.10.2021 at 09:22, Michal Simek wrote:
First of all subject is quite long. Please make it shorter and remove
dot at the end.
On 10/13/21 18:21, Adrian Fiergolski wrote:
When a caller is not interested in the returned message, the
On 14.10.2021 at 09:22, Michal Simek wrote:
>
> First of all subject is quite long. Please make it shorter and remove
> dot at the end.
>
>
> On 10/13/21 18:21, Adrian Fiergolski wrote:
>> When a caller is not interested in the returned message, the
>> ret_payload pointer is set to NULL in the
First of all subject is quite long. Please make it shorter and remove
dot at the end.
On 10/13/21 18:21, Adrian Fiergolski wrote:
When a caller is not interested in the returned message, the ret_payload
pointer is set to NULL in the u-boot-sources.
In this case, under EL3, the memory from
When a caller is not interested in the returned message, the ret_payload
pointer is set to NULL in the u-boot-sources.
In this case, under EL3, the memory from address 0x0 would be overwritten by
xilinx_pm_request with the returned IPI message,
damaging the original data under this address. The
6 matches
Mail list logo
