On Thu, Sep 19, 2024 at 10:54 AM Shuah Khan wrote:
>
> On 9/18/24 02:58, John Stultz wrote:
> > On Wed, Sep 18, 2024 at 2:47 AM Khem Raj wrote:
> >>
> >> Newer 32-bit architectures e.g. riscv32 are using 64-bit time_t
> >> from get go, they have not wired __NR_clock_adjtime at all
> >> valid-adjt
On 9/18/24 02:58, John Stultz wrote:
On Wed, Sep 18, 2024 at 2:47 AM Khem Raj wrote:
Newer 32-bit architectures e.g. riscv32 are using 64-bit time_t
from get go, they have not wired __NR_clock_adjtime at all
valid-adjtimex testcase fails to compile on such architectures.
if this condition is f
On Wed, Sep 18, 2024 at 2:47 AM Khem Raj wrote:
>
> Newer 32-bit architectures e.g. riscv32 are using 64-bit time_t
> from get go, they have not wired __NR_clock_adjtime at all
> valid-adjtimex testcase fails to compile on such architectures.
> if this condition is found then use 64-bit adjtime sy
Newer 32-bit architectures e.g. riscv32 are using 64-bit time_t
from get go, they have not wired __NR_clock_adjtime at all
valid-adjtimex testcase fails to compile on such architectures.
if this condition is found then use 64-bit adjtime syscall
Signed-off-by: Khem Raj
Cc: John Stultz
Cc: Shuah
