From: "Arnd Bergmann" <arnd@arndb.de>
To: "Pintu Kumar Agarwal" <pintu.ping@gmail.com>,
"Siddh Raman Pant" <sanganaka@siddh.me>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
kernelnewbies <kernelnewbies@kernelnewbies.org>
Subject: Re: Query: Y2038 patch series for 3.18 Kernel
Date: Tue, 04 Nov 2025 10:47:33 +0100 [thread overview]
Message-ID: <c40a0a35-ac43-4079-80ca-361bc8c9ae8a@app.fastmail.com> (raw)
In-Reply-To: <CAOuPNLhMcPJ_vkvyDKTW1c4TcSYusrzrAdu8khazHoy3txJGDw@mail.gmail.com>
On Tue, Nov 4, 2025, at 06:02, Pintu Kumar Agarwal wrote:
> On Mon, 3 Nov 2025 at 10:35, Siddh Raman Pant <sanganaka@siddh.me> wrote:
>>
>> Mon, 03 Nov 2025 09:57:18 +0530 को Pintu Kumar Agarwal ने लिखा :
>> > We have an arm32 based embedded product which is based on the 3.18
>> > kernel and a simple busybox.
>> > We wanted to support the Y2038 issue on this older kernel.
>> > Is this feasible
>> > Do we have the Y2038 separate patches available for both kernel and userspace
>> > ?
>> > Or upgrading the kernel is the only option ?
>>
>> Upgrading is a much much better option.
>>
> Yes, I understand, but upgrading the kernel on this older SoC brings
> more complexities, challenges and time taking.
> Customers also do not agree for the upgrade at this stage and they are
> looking for alternatives.
> So, we are exploring both the options right now.
>
> Are there any patchset maintained separately for this Y2038 issue for
> each kernel version to have a look ?
I used to maintain a 5.4 kernel with backports from the 5.6 patches,
but I would not recommend using that. Anything earlier than 5.4
is completely hopeless for 2038 because one would have to essentially
redo the changes from scratch.
Which chip exactly are you using?
Arnd
next prev parent reply other threads:[~2025-11-04 9:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-03 4:27 Pintu Kumar Agarwal
2025-11-03 5:04 ` Siddh Raman Pant
2025-11-04 5:02 ` Pintu Kumar Agarwal
2025-11-04 5:08 ` Greg KH
2025-11-04 9:47 ` Arnd Bergmann [this message]
2025-11-05 9:47 ` Pintu Kumar Agarwal
2025-11-06 8:17 ` Arnd Bergmann
2025-12-17 4:53 ` Pintu Kumar Agarwal
2026-01-20 1:05 ` syrus
2026-01-20 9:03 ` Arnd Bergmann
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=c40a0a35-ac43-4079-80ca-361bc8c9ae8a@app.fastmail.com \
--to=arnd@arndb.de \
--cc=kernelnewbies@kernelnewbies.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pintu.ping@gmail.com \
--cc=sanganaka@siddh.me \
/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
all inboxes | Powered by JetHome®