mbox series

[0/2] selftests/nolibc: run-user improvements

Message ID 20770915-nolibc-run-user-v1-0-3caec61726dc@weissschuh.net (mailing list archive)
Headers show
Series selftests/nolibc: run-user improvements | expand

Message

Thomas Weißschuh Sept. 15, 2077, 12:13 a.m. UTC
A small bugfix for "run-user XARCH=ppc64le" and run-user support for
run-tests.sh.

Signed-off-by: Thomas Weißschuh <linux@weissschuh.net>
---
Thomas Weißschuh (2):
      selftests/nolibc: introduce QEMU_ARCH_USER
      selftests/nolibc: run-tests.sh: enable testing via qemu-user

 tools/testing/selftests/nolibc/Makefile     |  5 ++++-
 tools/testing/selftests/nolibc/run-tests.sh | 22 +++++++++++++++++++---
 2 files changed, 23 insertions(+), 4 deletions(-)
---
base-commit: ba335752620565c25c3028fff9496bb8ef373602
change-id: 20770915-nolibc-run-user-845375a3ec4f

Best regards,

Comments

Konstantin Ryabitsev Nov. 9, 2023, 4:28 p.m. UTC | #1
On Wed, Sep 15, 2077 at 02:13:51AM +0200, Thomas Weißschuh wrote:
        ^^^^^^^^^^^^

I'm curious how this happened, especially since this was sent with b4.

-K
Willy Tarreau Nov. 9, 2023, 4:31 p.m. UTC | #2
On Thu, Nov 09, 2023 at 11:28:41AM -0500, Konstantin Ryabitsev wrote:
> On Wed, Sep 15, 2077 at 02:13:51AM +0200, Thomas Weißschuh wrote:
>         ^^^^^^^^^^^^
> 
> I'm curious how this happened, especially since this was sent with b4.

We didn't want to tell you, but you slept 54 years Konstantin, the
current kernel is version 41.8 ;-)

Willy
Konstantin Ryabitsev Nov. 9, 2023, 4:34 p.m. UTC | #3
On Thu, Nov 09, 2023 at 05:31:42PM +0100, Willy Tarreau wrote:
> > I'm curious how this happened, especially since this was sent with b4.
> 
> We didn't want to tell you, but you slept 54 years Konstantin, the
> current kernel is version 41.8 ;-)

Dang, I see we still use email for kernel development 50 years from now!

-K
Thomas Weißschuh Nov. 9, 2023, 5:44 p.m. UTC | #4
Nov 9, 2023 17:28:45 Konstantin Ryabitsev <konstantin@linuxfoundation.org>:

> On Wed, Sep 15, 2077 at 02:13:51AM +0200, Thomas Weißschuh wrote:
>         ^^^^^^^^^^^^
>
> I'm curious how this happened, especially since this was sent with b4.

My system time was messed up.
I blame systemd-timesyncd.
Konstantin Ryabitsev Nov. 9, 2023, 6:04 p.m. UTC | #5
On Thu, Nov 09, 2023 at 06:44:44PM +0100, Thomas Weißschuh  wrote:
> > On Wed, Sep 15, 2077 at 02:13:51AM +0200, Thomas Weißschuh wrote:
> >         ^^^^^^^^^^^^
> >
> > I'm curious how this happened, especially since this was sent with b4.
> 
> My system time was messed up.
> I blame systemd-timesyncd.

Well, at least we know b4 is Y38K compliant. ;)

Thank you!

-K
Shuah Khan Aug. 2, 2024, 9:13 p.m. UTC | #6
On 11/9/23 11:04, Konstantin Ryabitsev wrote:
> On Thu, Nov 09, 2023 at 06:44:44PM +0100, Thomas Weißschuh  wrote:
>>> On Wed, Sep 15, 2077 at 02:13:51AM +0200, Thomas Weißschuh wrote:
>>>          ^^^^^^^^^^^^
>>>
>>> I'm curious how this happened, especially since this was sent with b4.
>>
>> My system time was messed up.
>> I blame systemd-timesyncd.
> 
> Well, at least we know b4 is Y38K compliant. ;)
> 

And my nolibc email folder will show this thread as the latest
forever :)

thanks,
-- Shuah