mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Arnd Bergmann" <arnd@arndb.de>
To: syrus <syrus.lssu@ingenic.com>
Cc: "Siddh Raman Pant" <sanganaka@siddh.me>,
	linux-kernel@vger.kernel.org,
	kernelnewbies <kernelnewbies@kernelnewbies.org>,
	"Neil Armstrong" <neil.armstrong@linaro.org>,
	"[Syrus]" <syrus.lssu@ingenic.com>,
	"Paul Cercueil" <paul@crapouillou.net>
Subject: Re: Query: Y2038 patch series for 3.18 Kernel
Date: Tue, 20 Jan 2026 10:03:49 +0100	[thread overview]
Message-ID: <a0774317-01e8-4e2b-9514-ac9e36380720@app.fastmail.com> (raw)
In-Reply-To: <20260120010512.1951-1-syrus.lssu@ingenic.com>

On Tue, Jan 20, 2026, at 02:05, syrus wrote:
> From: [Syrus] <[syrus.lssu@ingenic.com]>
>
> Hi Arnd, all,
>
> Thanks for the discussion. While kernel upgrade solves Y2038 for new
> projects, our legacy devices on 3.10.14 kernel face upgrade challenges
> due to driver compatibility and limited resources (limited manpower, 
> communication barriers between different departments and companies, etc.).
>
> Has anyone successfully backported Y2038 fixes to older kernels like
> 3.10.x? I'm looking for patch summaries or experiences with such
> backports, or at least a summary of the commit history that addresses
> this issue. Any guidance on key subsystems to focus on would be very
> helpful for maintaining our legacy devices.

Hi Syrus,

As I replied earlier, anything older than 5.4 has pretty much no
chance of getting the kernel backports.

If you are specifically working on Ingenic's own SoC support,
I do think that you are in luck as these seem to be fairly well
supported in recent kernels, based on the work that Paul Cercueil
has done over the years, at least for the chips that ended up
in popular development boards and gaming handhelds (jz4725,
jz4740, jz4760, jz4770).

If there are specific drivers that are not yet supported upstream
but work on the patched 3.10 kernel, I'm sure you can find
consulting companies that are able to port those drivers as well.

     Arnd

      reply	other threads:[~2026-01-20  9:05 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
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 [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=a0774317-01e8-4e2b-9514-ac9e36380720@app.fastmail.com \
    --to=arnd@arndb.de \
    --cc=kernelnewbies@kernelnewbies.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=neil.armstrong@linaro.org \
    --cc=paul@crapouillou.net \
    --cc=sanganaka@siddh.me \
    --cc=syrus.lssu@ingenic.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 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®