From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: phil995511 <phil995511@proton.me>
Cc: "linus.walleij@linaro.org" <linus.walleij@linaro.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"arnd@arndb.de" <arnd@arndb.de>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"paulmck@kernel.org" <paulmck@kernel.org>
Subject: Re: [GIT PULL] Generic entry for ARM
Date: Sun, 2 Mar 2025 17:17:42 +0000 [thread overview]
Message-ID: <Z8SSthQ-gK686k8u@shell.armlinux.org.uk> (raw)
In-Reply-To: <0oXU8PP2CHCw1Qblhw1cKOTt90K2CLbHo4BLw9LOs-J1klN1Y_N7IagulWZHR7bGhmxyPXlZTOUEqVZDtwcXj9j93_BxdrdnmW7qk3uIrU4=@proton.me>
On Sun, Mar 02, 2025 at 03:23:20PM +0000, phil995511 wrote:
> It is a very bad idea to want to code the Linux kernel for ARM in C++ !!!
>
> Our ARM CPUs on RPi and others are not powerful enough to use a Linux kernel written in C++ and therefore lose performance, while these ARM CPUs are already extremely low-performance !!!
>
> Suggesting to code like this is to be in favor of planned obsolescence, of the scrapping of thousands of small machines ;-(
With all due respect, you have your knickers in a twist.
This is not about C++, it's about plain old fashioned C, which has been
the preferred kernel programming language for decades. I have no idea
where you've got the idea that LinusW's commit has anything to do with
C++.
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 80Mbps down 10Mbps up. Decent connectivity at last!
next prev parent reply other threads:[~2025-03-02 17:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-02 15:23 [GIT PULL] Generic entry for ARM phil995511
2025-03-02 17:17 ` Russell King (Oracle) [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-02-28 12:49 Linus Walleij
2025-03-12 11:13 ` Thomas Gleixner
2025-03-12 18:00 ` Paul E. McKenney
2025-03-31 21:48 ` Linus Walleij
2025-04-07 17:00 ` Paul E. McKenney
2025-04-07 23:47 ` Josh Poimboeuf
2025-04-08 0:14 ` Steven Rostedt
2025-04-09 14:54 ` Peter Zijlstra
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=Z8SSthQ-gK686k8u@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=arnd@arndb.de \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@kernel.org \
--cc=phil995511@proton.me \
--cc=tglx@linutronix.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;
as well as URLs for NNTP newsgroup(s).