qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Fam Zheng" <fam@euphon.net>,
	"Peter Maydell" <peter.maydell@linaro.org>,
	"Thomas Huth" <thuth@redhat.com>, "Ed Maste" <emaste@freebsd.org>,
	"Philippe Mathieu-Daudé" <philmd@redhat.com>,
	"Claudio Fontana" <cfontana@suse.de>,
	"Alex Bennée" <alex.bennee@linaro.org>,
	"Li-Wen Hsu" <lwhsu@freebsd.org>,
	"David Gibson" <david@gibson.dropbear.id.au>
Subject: [PATCH v2 0/5] tests: Remove unused bison/flex packages
Date: Fri, 15 May 2020 18:30:24 +0200	[thread overview]
Message-ID: <20200515163029.12917-1-philmd@redhat.com> (raw)

I was misguided by libdtc warnings, and thought bison/flex
were required to build QEMU, so installed them in docker
(and they also ended in the VM scripts).

Claudio's series "libfdt: build only the strict necessary"
even silents the warnings.

Based-on: <20200514193811.6798-1-cfontana@suse.de>

Philippe Mathieu-Daudé (5):
  tests/docker: Remove flex/bison packages
  tests/vm: Remove flex/bison packages
  gitlab-ci: Remove flex/bison packages
  cirrus-ci: Remove flex/bison packages
  scripts/coverity-scan: Remove flex/bison packages

 .cirrus.yml                                         | 2 +-
 .gitlab-ci.yml                                      | 2 +-
 scripts/coverity-scan/coverity-scan.docker          | 2 --
 tests/docker/dockerfiles/centos7.docker             | 2 --
 tests/docker/dockerfiles/centos8.docker             | 2 --
 tests/docker/dockerfiles/debian-xtensa-cross.docker | 2 --
 tests/docker/dockerfiles/debian10.docker            | 2 --
 tests/docker/dockerfiles/debian9.docker             | 2 --
 tests/docker/dockerfiles/fedora.docker              | 2 --
 tests/docker/dockerfiles/ubuntu.docker              | 2 +-
 tests/docker/dockerfiles/ubuntu1804.docker          | 2 +-
 tests/vm/fedora                                     | 1 -
 tests/vm/freebsd                                    | 1 -
 tests/vm/netbsd                                     | 1 -
 tests/vm/openbsd                                    | 1 -
 tests/vm/ubuntu.i386                                | 2 +-
 16 files changed, 5 insertions(+), 23 deletions(-)

-- 
2.21.3



             reply	other threads:[~2020-05-15 16:32 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-15 16:30 Philippe Mathieu-Daudé [this message]
2020-05-15 16:30 ` [PATCH v2 1/5] tests/docker: Remove flex/bison packages Philippe Mathieu-Daudé
2020-05-15 22:58   ` Claudio Fontana
2020-05-15 16:30 ` [PATCH v2 2/5] tests/vm: " Philippe Mathieu-Daudé
2020-05-15 22:56   ` Claudio Fontana
2020-05-15 16:30 ` [PATCH v2 3/5] gitlab-ci: " Philippe Mathieu-Daudé
2020-05-15 16:44   ` Thomas Huth
2020-05-15 16:30 ` [PATCH v2 4/5] cirrus-ci: " Philippe Mathieu-Daudé
2020-05-15 20:43   ` Li-Wen Hsu
2020-05-15 16:30 ` [PATCH v2 5/5] scripts/coverity-scan: " Philippe Mathieu-Daudé
2020-05-15 22:59   ` Claudio Fontana
2020-06-08 15:58 ` [PATCH v2 0/5] tests: Remove unused bison/flex packages Alex Bennée

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=20200515163029.12917-1-philmd@redhat.com \
    --to=philmd@redhat.com \
    --cc=alex.bennee@linaro.org \
    --cc=cfontana@suse.de \
    --cc=david@gibson.dropbear.id.au \
    --cc=emaste@freebsd.org \
    --cc=fam@euphon.net \
    --cc=lwhsu@freebsd.org \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=thuth@redhat.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).