Andrew,
> EXT email: be mindful of links/attachments.
>
> On 13/03/2025 9:27 am, Choi, Anderson wrote:
>> May I know when you think it would be mainlined? And will it be applied to
> all branches, like 4.19 and 4.20?
>
> FYI, backports of this and the xfree() bug have just happened, back to 4.18
On 13/03/2025 9:27 am, Choi, Anderson wrote:
> May I know when you think it would be mainlined? And will it be applied to
> all branches, like 4.19 and 4.20?
FYI, backports of this and the xfree() bug have just happened, back to 4.18.
~Andrew
On 13.03.25 10:27, Choi, Anderson wrote:
Juergen,
On 13.03.25 07:51, Choi, Anderson wrote:
We are observing an incorrect or unexpected behavior with ARINC653
scheduler when we set up multiple ARINC653 CPU pools and assign a
different number of domains to each CPU pool.
...
It seems there's
Juergen,
> On 13.03.25 07:51, Choi, Anderson wrote:
>> We are observing an incorrect or unexpected behavior with ARINC653
> scheduler when we set up multiple ARINC653 CPU pools and assign a
> different number of domains to each CPU pool.
>
> ...
>
>> It seems there's a corner condition in using
On 13.03.25 07:51, Choi, Anderson wrote:
We are observing an incorrect or unexpected behavior with ARINC653 scheduler
when we set up multiple ARINC653 CPU pools and assign a different number of
domains to each CPU pool.
...
It seems there's a corner condition in using the global variables "
