From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: Leonard Anderweit <L.Anderweit@phytec.de>
Cc: "arnd@arndb.de" <arnd@arndb.de>,
"linux-rtc@vger.kernel.org" <linux-rtc@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"upstream@phytec.de" <upstream@phytec.de>
Subject: Re: Question about [PATCH] [RFC] rtc: y2038: remove broken RTC_HCTOSYS workaround
Date: Fri, 28 Jun 2024 00:43:21 +0200 [thread overview]
Message-ID: <20240627224321db4557b2@mail.local> (raw)
In-Reply-To: <cf6ac9542f58a33b146ad7b0f5577e1dff3becab.camel@phytec.de>
On 24/06/2024 11:41:41+0000, Leonard Anderweit wrote:
> Hi,
>
> I found this patch [1] which is necessary for a project I'm currently
> working on. I'm using phyboard-wega [2] with an am335 ARM SoC which I
> want to make y2038 proof.
> Is there any reason it was never accepted?
>
The systemd maintainer think the kernel is well placed to take a
decision it can't actually take so they won't fix a bug where systemd is
crashing when userspace is 32bit.
The whole situation is frustrating and honestly, nobody should use the
hctosys insanity anyway. Obviously systemd mandates its usage and this
is yet another topic on which they think the kernel is better placed to
take decisions that are actually userspace policy.
I've been arguing for a while and gave up.
> [1]https://lore.kernel.org/all/20220908115337.1604277-1-arnd@kernel.org/
> [2]https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/tree/arch/arm/boot/dts/ti/omap/am335x-wega-rdk.dts
>
> Regards
> Leonard
--
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2024-06-27 22:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-24 11:41 Question about [PATCH] [RFC] rtc: y2038: remove broken RTC_HCTOSYS workaround Leonard Anderweit
2024-06-27 22:43 ` Alexandre Belloni [this message]
2024-06-28 6:01 ` Arnd Bergmann
2024-06-28 6:33 ` Stefan Müller-Klieser
2024-06-28 6:53 ` 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=20240627224321db4557b2@mail.local \
--to=alexandre.belloni@bootlin.com \
--cc=L.Anderweit@phytec.de \
--cc=arnd@arndb.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--cc=upstream@phytec.de \
/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