From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Waldemar Brodkorb <wbx@openadk.org>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 2/2] configs/qemu_riscv32_nommu_virt: new defconfig
Date: Sun, 12 May 2024 12:20:48 +0200 [thread overview]
Message-ID: <20240512122048.36a3f93b@windsurf> (raw)
In-Reply-To: <ZkCU03+ru07pxr5d@waldemar-brodkorb.de>
On Sun, 12 May 2024 12:07:15 +0200
Waldemar Brodkorb <wbx@openadk.org> wrote:
> Add new defconfig for Qemu RISCV32 w/o MMU.
>
> Signed-off-by: Waldemar Brodkorb <wbx@openadk.org>
> ---
> DEVELOPERS | 2 ++
> board/qemu/riscv32-virt/linux-nommu.config | 21 ++++++++++++
> .../patches/linux-headers/linux-headers.hash | 2 ++
> .../riscv32-virt/patches/linux/linux.hash | 2 ++
> board/qemu/riscv32-virt/readme.txt | 2 ++
> configs/qemu_riscv32_nommu_virt_defconfig | 34 +++++++++++++++++++
> 6 files changed, 63 insertions(+)
> create mode 100644 board/qemu/riscv32-virt/linux-nommu.config
> create mode 100644 board/qemu/riscv32-virt/patches/linux-headers/linux-headers.hash
> create mode 100644 board/qemu/riscv32-virt/patches/linux/linux.hash
> create mode 100644 configs/qemu_riscv32_nommu_virt_defconfig
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2024-05-12 10:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-12 10:07 [Buildroot] [PATCH 2/2] configs/qemu_riscv32_nommu_virt: new defconfig Waldemar Brodkorb
2024-05-12 10:20 ` Thomas Petazzoni via buildroot [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=20240512122048.36a3f93b@windsurf \
--to=buildroot@buildroot.org \
--cc=thomas.petazzoni@bootlin.com \
--cc=wbx@openadk.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 read-only IMAP folder(s) and NNTP newsgroup(s).