Em 24 de setembro de 2024 23:40:27 GMT+02:00, Gabriel Krisman Bertazi
escreveu:
>André Almeida writes:
>
>> Hey!
>>
>> On 9/23/24 19:34, Gabriela Bittencourt wrote:
>>> Instead of creating 'test' functions, use kunit functions to test
>>> utf-8 support in unicode subsystem.
>>
>> I think it w
André Almeida writes:
> Hey!
>
> On 9/23/24 19:34, Gabriela Bittencourt wrote:
>> Instead of creating 'test' functions, use kunit functions to test
>> utf-8 support in unicode subsystem.
>
> I think it would be nice to explain in the commit message what are the
> benefits of this change, why refa
Hey!
On 9/23/24 19:34, Gabriela Bittencourt wrote:
Instead of creating 'test' functions, use kunit functions to test
utf-8 support in unicode subsystem.
I think it would be nice to explain in the commit message what are the
benefits of this change, why refactoring into KUnit is a good idea?
The longest length of a symbol (KSYM_NAME_LEN) was increased to 512
in the reference [1]. This patch adds a kunit test to check the longest
symbol length.
This test can also help other efforts for longer symbol lenght,
like [2].
[1] https://lore.kernel.org/lkml/20220802015052.10452-6-oj...@kernel
On Tue, Sep 24, 2024 at 01:27:58PM +0200, Kevin Brodsky wrote:
> On 22/08/2024 17:11, Joey Gouly wrote:
> > @@ -1178,6 +1237,9 @@ static void setup_return(struct pt_regs *regs, struct
> > k_sigaction *ka,
> > sme_smstop();
> > }
> >
> > + if (system_supports_poe())
> > +
On 22/08/2024 17:11, Joey Gouly wrote:
> @@ -1178,6 +1237,9 @@ static void setup_return(struct pt_regs *regs, struct
> k_sigaction *ka,
> sme_smstop();
> }
>
> + if (system_supports_poe())
> + write_sysreg_s(POR_EL0_INIT, SYS_POR_EL0);
At the point where setu
