From: Palmer Dabbelt <palmer@rivosinc.com>
To: linux-riscv@lists.infradead.org, suagrfillet@gmail.com
Subject: [PATCH v2 0/2] riscv: correct pt_level name via pgtable_l5/4_enabled
Date: Tue, 29 Aug 2023 21:39:18 -0700 [thread overview]
Message-ID: <20230830044129.11481-1-palmer@rivosinc.com> (raw)
Sorry for just re-sending your patch, but I'd had this build fix
floating around as a suggestion and figured it'd be easier to just send
it so I can take this more quickly. That patch looks cleaner to me, but
happy to hear if anyone has a better way to do it.
Changes since v1 <20230712115740.943324-1-suagrfillet@gmail.com>:
* Fix the rv32 build with patch #1.
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next reply other threads:[~2023-08-30 13:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-30 4:39 Palmer Dabbelt [this message]
2023-08-30 4:39 ` [PATCH v2 1/2] RISC-V: Provide pgtable_l5_enabled on rv32 Palmer Dabbelt
2023-08-31 16:27 ` Conor Dooley
2023-08-30 4:39 ` [PATCH v2 2/2] riscv: correct pt_level name via pgtable_l5/4_enabled Palmer Dabbelt
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=20230830044129.11481-1-palmer@rivosinc.com \
--to=palmer@rivosinc.com \
--cc=linux-riscv@lists.infradead.org \
--cc=suagrfillet@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;
as well as URLs for NNTP newsgroup(s).