From: Alexander Kanavin <alex.kanavin@gmail.com>
To: openembedded-core@lists.openembedded.org
Cc: Alexander Kanavin <alex@linutronix.de>
Subject: [PATCH 5/5] time64.inc: add links to "Y2038 in Yocto" slides and video
Date: Mon, 16 Feb 2026 14:33:51 +0100 [thread overview]
Message-ID: <20260216133351.1034740-5-alex.kanavin@gmail.com> (raw)
In-Reply-To: <20260216133351.1034740-1-alex.kanavin@gmail.com>
From: Alexander Kanavin <alex@linutronix.de>
I'm not sure if placing conference slides and video links
here is okay, but I believe this is the best starting point
for anyone dealing with the Y2038 problem. It will help and
provide important context and action points for those needing
to support 32 bit products beyond Y2038.
Signed-off-by: Alexander Kanavin <alex@linutronix.de>
---
meta/conf/distro/include/time64.inc | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/meta/conf/distro/include/time64.inc b/meta/conf/distro/include/time64.inc
index 5a2a3fbe81..19177b1f3c 100644
--- a/meta/conf/distro/include/time64.inc
+++ b/meta/conf/distro/include/time64.inc
@@ -1,3 +1,8 @@
+# An overview of Y2038 issues, and how to prepare a yocto-based
+# product for that date is available at
+# https://www.youtube.com/watch?v=eaOHJHFMobw
+# https://osseu2024.sched.com/event/1ej4C/
+#
# To simulate Y2038 occurring in qemu, add to your build configuration:
# QB_OPT_APPEND:append = " -rtc base=2040-02-02"
#
--
2.47.3
prev parent reply other threads:[~2026-02-16 13:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-16 13:33 [PATCH 1/5] lttng-tools: ensure that ptest errors are not suppressed Alexander Kanavin
2026-02-16 13:33 ` [PATCH 2/5] lttng-tools: add missing python3-multiprocessing dependency to ptests Alexander Kanavin
2026-02-16 13:33 ` [PATCH 3/5] lttng-tools: install .expect test files with a wildcard Alexander Kanavin
2026-02-16 13:33 ` [PATCH 4/5] time64.inc: clean up and add upstream tickets where issues remain Alexander Kanavin
2026-02-16 13:33 ` Alexander Kanavin [this message]
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=20260216133351.1034740-5-alex.kanavin@gmail.com \
--to=alex.kanavin@gmail.com \
--cc=alex@linutronix.de \
--cc=openembedded-core@lists.openembedded.org \
/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