From: Linus Torvalds <torvalds@linux-foundation.org>
To: Ben Dooks <ben.dooks@codethink.co.uk>
Cc: Paul Walmsley <pjw@kernel.org>,
linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] RISC-V updates for v6.18-rc1
Date: Tue, 30 Sep 2025 09:04:19 -0700 [thread overview]
Message-ID: <CAHk-=wgfpswvq0TypePyjv3dofO5YaUC_fSd_MjzY7jogCUnCg@mail.gmail.com> (raw)
In-Reply-To: <066d70c7-b0a7-45e5-9337-17901bc95664@codethink.co.uk>
On Tue, 30 Sept 2025 at 00:25, Ben Dooks <ben.dooks@codethink.co.uk> wrote:
>
> Is there any chance some of the big-endian work we did is getting in
> for this round?
Oh Christ. Is somebody seriously working on BE support in 2025?
WHY?
Seriously, that sounds like just *stupid*. Is there some actual real
reason for this, or is it more of the "RISC-V is used in academic
design classes and so people just want to do endianness for academic
reasons"?
Because I'd be more than happy to just draw a line in the sand and say
"New endianness problems are somebody ELSES problem", and tell people
to stop being silly.
Let's not complicate things for no good reason. And there is *NO*
reason to add new endianness.
RISC-V is enough of a mess with the millions of silly configuration
issues already. Don't make it even worse.
Tell people to just talk to their therapists instead. That's *much*
more productive.
Really.
Linus
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2025-09-30 16:04 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-29 8:00 [GIT PULL] RISC-V updates for v6.18-rc1 Paul Walmsley
2025-09-30 2:54 ` pr-tracker-bot
2025-09-30 7:25 ` Ben Dooks
2025-09-30 16:04 ` Linus Torvalds [this message]
2025-09-30 23:53 ` Linus Torvalds
2025-10-01 18:33 ` Eric Biggers
2025-10-03 1:45 ` Yury Norov
2025-10-01 19:02 ` Conor Dooley
2025-10-01 19:39 ` Linus Torvalds
2025-10-02 12:48 ` Ben Dooks
2025-10-02 15:06 ` Olof Johansson
2025-10-02 15:22 ` Ben Dooks
2025-10-07 23:43 ` Maciej W. Rozycki
2025-10-20 23:31 ` Paul Walmsley
2025-10-02 18:08 ` Theodore Ts'o
2025-10-11 8:38 ` Yao Zi
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='CAHk-=wgfpswvq0TypePyjv3dofO5YaUC_fSd_MjzY7jogCUnCg@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--cc=ben.dooks@codethink.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=pjw@kernel.org \
/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).