From: Nam Cao <namcao@linutronix.de>
To: CABe3_aH6jYyoC=Jx91qATP2kOoY42NUtesyZpGbWGoQTw75OAA@mail.gmail.com,
cmirabil@redhat.com
Cc: alex@ghiti.fr, aou@eecs.berkeley.edu, haxel@fzi.de,
linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org,
palmer@dabbelt.com, pjw@kernel.org, vitaly.wool@konsulko.com,
Kunwu Chan <kunwu.chan@linux.dev>,
Zhouyi Zhou zhou <zhouyi@gmail.com>,
igor.b@beldev.am, Jisheng Zhang <jszhang@kernel.org>,
Albert Ou <aou@eecs.berkeley.edu>, Frederik Haxel <haxel@fzi.de>,
charlie@rivosinc.com
Subject: Re: [PATCH] riscv: Remove support for XIP kernel
Date: Mon, 01 Jun 2026 10:26:40 +0200 [thread overview]
Message-ID: <87pl2awtrz.fsf@yellow.woof> (raw)
In-Reply-To: <05290c17-d55f-4e60-a77e-c36c3f14a89a@redhat.com>
Jesse Taube-Perrotta <jtaubepe@redhat.com> writes:
> TLDR: Is re-adding XIP to no-mmu rv32 a possibility
Paul explained the requirements to keep XIP:
https://lore.kernel.org/linux-riscv/609b889a-8bb1-d2b5-8de6-ddeec27cac04@kernel.org/
Nam
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
prev parent reply other threads:[~2026-06-01 8:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-02 11:54 [PATCH] riscv: Remove support for XIP kernel Nam Cao
2026-02-13 0:17 ` Paul Walmsley
2026-02-13 0:22 ` Conor Dooley
2026-02-13 9:37 ` Kunwu Chan
[not found] ` <CAM4kBBK=b73LZQesfypJ95+68aM_oAp3-VZ2BcGNm2NK6UpK7w@mail.gmail.com>
2026-02-13 9:48 ` igor.b
2026-02-13 10:43 ` Conor Dooley
2026-02-20 15:16 ` Jisheng Zhang
2026-02-20 15:20 ` Jisheng Zhang
2026-03-20 16:04 ` Charles Mirabile
2026-03-26 16:45 ` Nam Cao
2026-03-26 17:37 ` Charles Mirabile
2026-05-29 17:20 ` Jesse Taube-Perrotta
2026-06-01 8:26 ` Nam Cao [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=87pl2awtrz.fsf@yellow.woof \
--to=namcao@linutronix.de \
--cc=CABe3_aH6jYyoC=Jx91qATP2kOoY42NUtesyZpGbWGoQTw75OAA@mail.gmail.com \
--cc=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=charlie@rivosinc.com \
--cc=cmirabil@redhat.com \
--cc=haxel@fzi.de \
--cc=igor.b@beldev.am \
--cc=jszhang@kernel.org \
--cc=kunwu.chan@linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=pjw@kernel.org \
--cc=vitaly.wool@konsulko.com \
--cc=zhouyi@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox