qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: qemu-devel@nongnu.org
Cc: famz@redhat.com, kwolf@redhat.com, vsementsov@virtuozzo.com,
	qemu-block@nongnu.org, armbru@redhat.com, mreitz@redhat.com,
	pbonzini@redhat.com, jsnow@redhat.com
Subject: Re: [Qemu-devel] [PATCH] nbd/client: add x-block-status hack for testing server
Date: Fri, 29 Jun 2018 10:53:39 -0500	[thread overview]
Message-ID: <cce24450-9dc9-d5d6-584a-5da11cb7db29@redhat.com> (raw)
In-Reply-To: <152956038747.819.14972444362425747616@d39dc562802a>

On 06/21/2018 12:53 AM, no-reply@patchew.org wrote:
> Hi,
> 
> This series failed docker-mingw@fedora build test. Please find the testing commands and
> their output below. If you have Docker installed, you can probably reproduce it
> locally.

>    CC      crypto/hmac-nettle.o
> /tmp/qemu-test/src/nbd/client.c: In function 'nbd_negotiate_simple_meta_context':
> /tmp/qemu-test/src/nbd/client.c:738:28: error: implicit declaration of function 'strchrnul'; did you mean 'strchr'? [-Werror=implicit-function-declaration]
>       uint32_t context_len = strchrnul(context, ';') - context;
>                              ^~~~~~~~~
>                              strchr

If I keep the semicolon-separated string (which I really don't want to 
do in v2), then I'd obviously have to rebase this on top of the proposed 
patch adding qemu_strchrnul.

-- 
Eric Blake, Principal Software Engineer
Red Hat, Inc.           +1-919-301-3266
Virtualization:  qemu.org | libvirt.org

  reply	other threads:[~2018-06-29 15:53 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-21  3:25 [Qemu-devel] [PATCH] nbd/client: add x-block-status hack for testing server Eric Blake
2018-06-21  5:45 ` no-reply
2018-06-21 15:09   ` Eric Blake
2018-06-21  5:53 ` no-reply
2018-06-29 15:53   ` Eric Blake [this message]
2018-06-25 13:50 ` Max Reitz
2018-06-25 17:12   ` John Snow
2018-06-29 10:01 ` Vladimir Sementsov-Ogievskiy
2018-06-29 15:55   ` Eric Blake

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=cce24450-9dc9-d5d6-584a-5da11cb7db29@redhat.com \
    --to=eblake@redhat.com \
    --cc=armbru@redhat.com \
    --cc=famz@redhat.com \
    --cc=jsnow@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=mreitz@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=vsementsov@virtuozzo.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).