Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/qemu: move patch 3 to the 3.1.1.1 subdir
Date: Mon, 21 Oct 2019 19:09:03 +0200	[thread overview]
Message-ID: <20191021190903.10e62578@windsurf> (raw)
In-Reply-To: <20191021124139.28615-1-unixmania@gmail.com>

Hello Carlos,

On Mon, 21 Oct 2019 09:41:39 -0300
unixmania at gmail.com wrote:

> From: Carlos Santos <unixmania@gmail.com>
> 
> Required since the bump from 3.1.1.
> 
> Signed-off-by: Carlos Santos <unixmania@gmail.com>
> ---
> Do we really need the subdir? I know that qemu keeps four releases but
> as far as I know Buildroot always included only one. Are there plans to
> add a configuration to choose the qemu version?

There is already such a version selection:

ifeq ($(BR2_csky),y)
QEMU_VERSION = b517e1dc3125a57555d67a8deed9eac7b42288e2
QEMU_SITE = $(call github,c-sky,qemu,$(QEMU_VERSION))
else
QEMU_VERSION = 3.1.1.1
QEMU_SOURCE = qemu-$(QEMU_VERSION).tar.xz
QEMU_SITE = http://download.qemu.org
endif

So we want the patches to only apply when the upstream 3.1.1.1 version
is used, and not when the C-SKY specific version is used.

>  ...0003-util-cacheinfo-fix-crash-when-compiling-with-uClibc.patch | 0
>  1 file changed, 0 insertions(+), 0 deletions(-)
>  rename package/qemu/{3.1.1 => 3.1.1.1}/0003-util-cacheinfo-fix-crash-when-compiling-with-uClibc.patch (100%)

Applied to master, thanks.

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2019-10-21 17:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-21 12:41 [Buildroot] [PATCH] package/qemu: move patch 3 to the 3.1.1.1 subdir unixmania at gmail.com
2019-10-21 17:09 ` Thomas Petazzoni [this message]
2019-10-21 17:57   ` Carlos Santos
2019-10-30  8:59 ` Peter Korsgaard

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=20191021190903.10e62578@windsurf \
    --to=thomas.petazzoni@bootlin.com \
    --cc=buildroot@busybox.net \
    /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