From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Laurent Vivier <laurent@vivier.eu>
Cc: qemu-devel@nongnu.org, Riku Voipio <riku.voipio@iki.fi>,
Gerd Hoffmann <kraxel@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v2 3/5] sockets: avoid string truncation warnings when copying UNIX path
Date: Thu, 2 May 2019 16:48:49 +0100 [thread overview]
Message-ID: <20190502154849.GH15718@redhat.com> (raw)
In-Reply-To: <a0e3bdd6-6003-1fb9-4d52-315b6441e966@vivier.eu>
On Thu, May 02, 2019 at 05:45:30PM +0200, Laurent Vivier wrote:
> Dan,
>
> do you want I take this through the trivial branch queue or do you add
> it into the Sockets branch queue?
I'm fine with you sending it via trivial queue since there's nothing
else pending for the sockets code.
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
WARNING: multiple messages have this Message-ID (diff)
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Laurent Vivier <laurent@vivier.eu>
Cc: Riku Voipio <riku.voipio@iki.fi>,
qemu-devel@nongnu.org, Gerd Hoffmann <kraxel@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v2 3/5] sockets: avoid string truncation warnings when copying UNIX path
Date: Thu, 2 May 2019 16:48:49 +0100 [thread overview]
Message-ID: <20190502154849.GH15718@redhat.com> (raw)
Message-ID: <20190502154849.qhArNq6fq18oDj4dOMEJFWcOkPM6xMa7xex9VSzH0vA@z> (raw)
In-Reply-To: <a0e3bdd6-6003-1fb9-4d52-315b6441e966@vivier.eu>
On Thu, May 02, 2019 at 05:45:30PM +0200, Laurent Vivier wrote:
> Dan,
>
> do you want I take this through the trivial branch queue or do you add
> it into the Sockets branch queue?
I'm fine with you sending it via trivial queue since there's nothing
else pending for the sockets code.
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2019-05-02 15:48 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-12 12:16 [Qemu-devel] [PATCH v2 0/5] misc set of fixes for warnings under GCC 9 Daniel P. Berrangé
2019-04-12 12:16 ` Daniel P. Berrangé
2019-04-12 12:16 ` [Qemu-devel] [PATCH v2 1/5] linux-user: avoid string truncation warnings in uname field copying Daniel P. Berrangé
2019-04-12 12:16 ` Daniel P. Berrangé
2019-04-12 12:28 ` Laurent Vivier
2019-04-12 12:28 ` Laurent Vivier
2019-04-12 12:16 ` [Qemu-devel] [PATCH v2 2/5] linux-user: avoid string truncation warnings in elf " Daniel P. Berrangé
2019-04-12 12:16 ` Daniel P. Berrangé
2019-04-12 12:32 ` Laurent Vivier
2019-04-12 12:32 ` Laurent Vivier
2019-04-12 12:16 ` [Qemu-devel] [PATCH v2 3/5] sockets: avoid string truncation warnings when copying UNIX path Daniel P. Berrangé
2019-04-12 12:16 ` Daniel P. Berrangé
2019-05-02 15:45 ` Laurent Vivier
2019-05-02 15:45 ` Laurent Vivier
2019-05-02 15:48 ` Daniel P. Berrangé [this message]
2019-05-02 15:48 ` Daniel P. Berrangé
2019-05-02 16:18 ` Laurent Vivier
2019-05-02 16:18 ` Laurent Vivier
2019-04-12 12:16 ` [Qemu-devel] [PATCH v2 4/5] hw/usb: avoid format truncation warning when formatting port name Daniel P. Berrangé
2019-04-12 12:16 ` Daniel P. Berrangé
2019-05-02 6:44 ` Gerd Hoffmann
2019-05-02 6:44 ` Gerd Hoffmann
2019-04-12 12:16 ` [Qemu-devel] [PATCH v2 5/5] qxl: avoid unaligned pointer reads/writes Daniel P. Berrangé
2019-04-12 12:16 ` Daniel P. Berrangé
2019-05-07 7:54 ` Gerd Hoffmann
2019-05-07 8:11 ` Philippe Mathieu-Daudé
2019-05-07 8:53 ` Gerd Hoffmann
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=20190502154849.GH15718@redhat.com \
--to=berrange@redhat.com \
--cc=kraxel@redhat.com \
--cc=laurent@vivier.eu \
--cc=qemu-devel@nongnu.org \
--cc=riku.voipio@iki.fi \
/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).