From: Miroslav Rezanina <mrezanin@redhat.com>
To: qemu-devel@nongnu.org
Subject: [PATCH v2 0/2] Fixing several GCC 11 warnings
Date: Mon, 11 Jan 2021 18:09:39 +0100 [thread overview]
Message-ID: <cover.1610384501.git.mrezanin@redhat.com> (raw)
Compiling qemu using GCC 11 we got several new warnings. To allow
build with --enable-werror, we need to solve issues generating these
warnings.
Signed-of-by: Miroslav Rezanina <mrezanin@redhat.com>
v2:
- Patch 2 rewrite to use strpadcpy
- removed Patch 3 (different version sent by Philippe Mathieu-Daudé)
Miroslav Rezanina (2):
Fix net.c warning on GCC 11
s390x: Fix vm name copy length
net/eth.c | 3 +++
target/s390x/kvm.c | 12 +++++-------
target/s390x/misc_helper.c | 7 +++++--
3 files changed, 13 insertions(+), 9 deletions(-)
--
2.18.4
next reply other threads:[~2021-01-11 17:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-11 17:09 Miroslav Rezanina [this message]
2021-01-11 17:09 ` [PATCH v2 1/2] Fix net.c warning on GCC 11 Miroslav Rezanina
2021-01-11 17:09 ` [PATCH v2 2/2] s390x: Use strpadcpy for copying vm name Miroslav Rezanina
2021-01-11 18:02 ` Philippe Mathieu-Daudé
2021-01-12 9:09 ` Thomas Huth
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=cover.1610384501.git.mrezanin@redhat.com \
--to=mrezanin@redhat.com \
--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).