Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Waldemar Brodkorb <wbx@openadk.org>
Cc: Romain Naour <romain.naour@gmail.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/qemu: update to 9.0.0
Date: Mon, 13 May 2024 22:49:49 +0200	[thread overview]
Message-ID: <20240513224949.169828d9@windsurf> (raw)
In-Reply-To: <ZkDCDNPE1sawl6SP@waldemar-brodkorb.de>

Hello,

On Sun, 12 May 2024 15:20:12 +0200
Waldemar Brodkorb <wbx@openadk.org> wrote:

> diff --git a/package/qemu/0002-softmmu-qemu-seccomp.c-add-missing-header-for-CLONE_.patch b/package/qemu/0002-softmmu-qemu-seccomp.c-add-missing-header-for-CLONE_.patch
> deleted file mode 100644
> index 91506b14d9..0000000000
> --- a/package/qemu/0002-softmmu-qemu-seccomp.c-add-missing-header-for-CLONE_.patch
> +++ /dev/null

The removal of this patch needed a .checkpackageignore change, so I did that.

> diff --git a/package/qemu/Config.in b/package/qemu/Config.in
> index 8d53ced300..91e0de884f 100644
> --- a/package/qemu/Config.in
> +++ b/package/qemu/Config.in
> @@ -289,7 +289,7 @@ config BR2_PACKAGE_QEMU_TARGET_RISCV32
>  	bool "riscv32"
>  	select BR2_PACKAGE_QEMU_FDT if BR2_PACKAGE_QEMU_SYSTEM
>  	help
> -	  RISC-V 33-bit architecture.
> +	  RISC-V 32-bit architecture.

This typo fix was unrelated to the bump, so it should have been a
separate patch. Therefore I made a separate commit.

Applied with those changes, thanks!

Thomas
-- 
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      reply	other threads:[~2024-05-13 20:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-12 13:20 [Buildroot] [PATCH] package/qemu: update to 9.0.0 Waldemar Brodkorb
2024-05-13 20:49 ` 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=20240513224949.169828d9@windsurf \
    --to=buildroot@buildroot.org \
    --cc=romain.naour@gmail.com \
    --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