From: Thomas Huth <thuth@redhat.com>
To: peter.maydell@linaro.org, qemu-devel@nongnu.org
Subject: [PULL 0/9] Fuzzer, configure, gitlab and misc patches
Date: Mon, 13 Jul 2020 12:55:25 +0200 [thread overview]
Message-ID: <20200713105534.10872-1-thuth@redhat.com> (raw)
Hi Peter,
the following changes since commit 9f526fce49c6ac48114ed04914b5a76e4db75785:
Merge remote-tracking branch 'remotes/stsquad/tags/pull-testing-and-misc-110720-2' into staging (2020-07-12 15:32:05 +0100)
are available in the Git repository at:
https://gitlab.com/huth/qemu.git tags/pull-request-2020-07-13
for you to fetch changes up to 2a84f48c2b387877422ee85f6425d2c1b25bace0:
docs/system/s390x: Improve the 3270 documentation (2020-07-13 11:40:52 +0200)
----------------------------------------------------------------
* Some fuzzer related fixes
* Fixes / improvements for the "configure" script
* Doc updates
* Gitlab pipeline-status script
----------------------------------------------------------------
Alexander Bulekov (2):
configure: do not clobber CFLAGS with --enable-fuzzing
fuzz: add missing header for rcu_enable_atfork
Cleber Rosa (1):
GitLab Gating CI: introduce pipeline-status contrib script
Olaf Hering (1):
configure: fix malloc check
Thomas Huth (5):
tests/qtest/fuzz: Add missing spaces in description
docs/devel/fuzzing: Fix bugs in documentation
Remove the CONFIG_PRAGMA_DIAGNOSTIC_AVAILABLE switch
disas/sh4: Add missing fallthrough annotations
docs/system/s390x: Improve the 3270 documentation
configure | 32 +-------
disas/sh4.c | 2 +
docs/devel/fuzzing.txt | 6 +-
docs/system/s390x/3270.rst | 43 ++++++++--
include/ui/gtk.h | 4 -
include/ui/qemu-pixman.h | 4 -
scripts/ci/gitlab-pipeline-status | 157 ++++++++++++++++++++++++++++++++++++
scripts/decodetree.py | 12 +--
tests/qtest/fuzz/fuzz.c | 1 +
tests/qtest/fuzz/virtio_scsi_fuzz.c | 4 +-
ui/gtk.c | 4 -
util/coroutine-ucontext.c | 4 +-
12 files changed, 210 insertions(+), 63 deletions(-)
create mode 100755 scripts/ci/gitlab-pipeline-status
next reply other threads:[~2020-07-13 10:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-13 10:55 Thomas Huth [this message]
2020-07-13 10:55 ` [PULL 1/9] configure: fix malloc check Thomas Huth
2020-07-13 10:55 ` [PULL 2/9] configure: do not clobber CFLAGS with --enable-fuzzing Thomas Huth
2020-07-13 10:55 ` [PULL 3/9] fuzz: add missing header for rcu_enable_atfork Thomas Huth
2020-07-13 10:55 ` [PULL 4/9] tests/qtest/fuzz: Add missing spaces in description Thomas Huth
2020-07-13 10:55 ` [PULL 5/9] docs/devel/fuzzing: Fix bugs in documentation Thomas Huth
2020-07-13 10:55 ` [PULL 6/9] Remove the CONFIG_PRAGMA_DIAGNOSTIC_AVAILABLE switch Thomas Huth
2020-07-13 10:55 ` [PULL 7/9] disas/sh4: Add missing fallthrough annotations Thomas Huth
2020-07-13 10:55 ` [PULL 8/9] GitLab Gating CI: introduce pipeline-status contrib script Thomas Huth
2020-07-13 10:55 ` [PULL 9/9] docs/system/s390x: Improve the 3270 documentation Thomas Huth
2020-07-13 11:27 ` [PULL 0/9] Fuzzer, configure, gitlab and misc patches no-reply
2020-07-13 13:35 ` Peter Maydell
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=20200713105534.10872-1-thuth@redhat.com \
--to=thuth@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.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 NNTP newsgroup(s).