From: Auger Eric <eric.auger@redhat.com>
To: Eric Blake <eblake@redhat.com>,
qemu-devel@nongnu.org, no-reply@patchew.org
Cc: fam@euphon.net, aik@ozlabs.ru, alex.williamson@redhat.com,
groug@kaod.org, eric.auger.pro@gmail.com
Subject: Re: [Qemu-devel] [PATCH v2] hw/vfio/common: Refactor container initialization
Date: Wed, 23 Jan 2019 16:31:36 +0100 [thread overview]
Message-ID: <2c8154ca-0e6f-8c52-dced-9dda1bb7ea4d@redhat.com> (raw)
In-Reply-To: <47263739-35c6-b711-dc94-3af62f5a2bbe@redhat.com>
Hi Eric,
On 1/23/19 4:01 PM, Eric Blake wrote:
> On 1/23/19 8:44 AM, Auger Eric wrote:
>
>>> /tmp/qemu-test/src/block/sheepdog.c: In function 'find_vdi_name':
>>> /tmp/qemu-test/src/block/sheepdog.c:1239:5: error: 'strncpy' specified bound 256 equals destination size [-Werror=stringop-truncation]
>>> strncpy(buf + SD_MAX_VDI_LEN, tag, SD_MAX_VDI_TAG_LEN);
>>> ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>> does not seem to be related to my patch.
>
> Known false alarm; the patchew processing queue is backlogged, and is
> testing patches against a version of qemu.git that does not yet have
> patches for newer gcc compliance incorporated, while at the same time
> having recently upgraded its testing environment to use the newer gcc
> that warns. Commit 97b583f4 will silence the noise, once patchew
> catches up to using it.
Thank you for the explanation.
Eric
>
prev parent reply other threads:[~2019-01-23 15:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-17 21:02 [Qemu-devel] [PATCH v2] hw/vfio/common: Refactor container initialization Eric Auger
2019-01-18 4:51 ` Alexey Kardashevskiy
2019-01-18 8:52 ` Auger Eric
2019-01-18 8:52 ` Greg Kurz
2019-01-23 14:23 ` no-reply
2019-01-23 14:44 ` Auger Eric
2019-01-23 15:01 ` Eric Blake
2019-01-23 15:31 ` Auger Eric [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=2c8154ca-0e6f-8c52-dced-9dda1bb7ea4d@redhat.com \
--to=eric.auger@redhat.com \
--cc=aik@ozlabs.ru \
--cc=alex.williamson@redhat.com \
--cc=eblake@redhat.com \
--cc=eric.auger.pro@gmail.com \
--cc=fam@euphon.net \
--cc=groug@kaod.org \
--cc=no-reply@patchew.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).