Linux Kernel Selftest development
 help / color / mirror / Atom feed
From: Shuah Khan <skhan@linuxfoundation.org>
To: "Konstantin Ryabitsev" <konstantin@linuxfoundation.org>,
	"Thomas Weißschuh" <thomas@t-8ch.de>
Cc: "Thomas Weißschuh" <linux@weissschuh.net>,
	"Willy Tarreau" <w@1wt.eu>, "Shuah Khan" <shuah@kernel.org>,
	linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org,
	"Shuah Khan" <skhan@linuxfoundation.org>
Subject: Re: [PATCH 0/2] selftests/nolibc: run-user improvements
Date: Fri, 2 Aug 2024 15:13:50 -0600	[thread overview]
Message-ID: <ca0470e3-f3f2-4e39-8170-9287fa8eb043@linuxfoundation.org> (raw)
In-Reply-To: <pfzkuw4o7752mb2ksowte2cbfa2ogd2bsucbget5nsk76edcin@tueappcjnih4>

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


  reply	other threads:[~2024-08-02 21:13 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2077-09-15  0:13 [PATCH 0/2] selftests/nolibc: run-user improvements Thomas Weißschuh
2023-11-09 16:28 ` Konstantin Ryabitsev
2023-11-09 16:31   ` Willy Tarreau
2023-11-09 16:34     ` Konstantin Ryabitsev
2023-11-09 17:44   ` Thomas Weißschuh 
2023-11-09 18:04     ` Konstantin Ryabitsev
2024-08-02 21:13       ` Shuah Khan [this message]
2077-09-15  0:13 ` [PATCH 1/2] selftests/nolibc: introduce QEMU_ARCH_USER Thomas Weißschuh
2077-09-15  0:13 ` [PATCH 2/2] selftests/nolibc: run-tests.sh: enable testing via qemu-user Thomas Weißschuh

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ca0470e3-f3f2-4e39-8170-9287fa8eb043@linuxfoundation.org \
    --to=skhan@linuxfoundation.org \
    --cc=konstantin@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=linux@weissschuh.net \
    --cc=shuah@kernel.org \
    --cc=thomas@t-8ch.de \
    --cc=w@1wt.eu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox