From: Greg KH <greg@kroah.com>
To: Pintu Kumar Agarwal <pintu.ping@gmail.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
Arnd Bergmann <arnd@arndb.de>,
kernelnewbies <kernelnewbies@kernelnewbies.org>
Subject: Re: Query: Y2038 patch series for 3.18 Kernel
Date: Tue, 4 Nov 2025 14:08:48 +0900 [thread overview]
Message-ID: <2025110403-backward-skeleton-305e@gregkh> (raw)
In-Reply-To: <CAOuPNLhMcPJ_vkvyDKTW1c4TcSYusrzrAdu8khazHoy3txJGDw@mail.gmail.com>
On Tue, Nov 04, 2025 at 10:32:28AM +0530, 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 ?
Nope, sorry. Please just update to a newer kernel version, that is the
only way forward (and as a bonus, you actually will have tens of
thousands of bugs fixed on your system.)
good luck!
greg k-h
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
WARNING: multiple messages have this Message-ID (diff)
From: Greg KH <greg@kroah.com>
To: Pintu Kumar Agarwal <pintu.ping@gmail.com>
Cc: Siddh Raman Pant <sanganaka@siddh.me>,
linux-kernel <linux-kernel@vger.kernel.org>,
Arnd Bergmann <arnd@arndb.de>,
kernelnewbies <kernelnewbies@kernelnewbies.org>
Subject: Re: Query: Y2038 patch series for 3.18 Kernel
Date: Tue, 4 Nov 2025 14:08:48 +0900 [thread overview]
Message-ID: <2025110403-backward-skeleton-305e@gregkh> (raw)
In-Reply-To: <CAOuPNLhMcPJ_vkvyDKTW1c4TcSYusrzrAdu8khazHoy3txJGDw@mail.gmail.com>
On Tue, Nov 04, 2025 at 10:32:28AM +0530, 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 ?
Nope, sorry. Please just update to a newer kernel version, that is the
only way forward (and as a bonus, you actually will have tens of
thousands of bugs fixed on your system.)
good luck!
greg k-h
next prev parent reply other threads:[~2025-11-04 5:08 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-03 4:27 Query: Y2038 patch series for 3.18 Kernel Pintu Kumar Agarwal
2025-11-03 4:27 ` Pintu Kumar Agarwal
2025-11-03 5:04 ` Siddh Raman Pant
2025-11-03 5:04 ` Siddh Raman Pant
2025-11-04 5:02 ` Pintu Kumar Agarwal
2025-11-04 5:02 ` Pintu Kumar Agarwal
2025-11-04 5:08 ` Greg KH [this message]
2025-11-04 5:08 ` Greg KH
2025-11-04 9:47 ` Arnd Bergmann
2025-11-04 9:47 ` Arnd Bergmann
2025-11-05 9:47 ` Pintu Kumar Agarwal
2025-11-05 9:47 ` Pintu Kumar Agarwal
2025-11-06 8:17 ` Arnd Bergmann
2025-11-06 8:17 ` Arnd Bergmann
2025-12-17 4:53 ` Pintu Kumar Agarwal
2025-12-17 4:53 ` Pintu Kumar Agarwal
2026-01-20 1:05 ` syrus
2026-01-20 9:03 ` Arnd Bergmann
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=2025110403-backward-skeleton-305e@gregkh \
--to=greg@kroah.com \
--cc=arnd@arndb.de \
--cc=kernelnewbies@kernelnewbies.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pintu.ping@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.