From: Eric Blake <eblake@redhat.com>
To: Programmingkid <programmingkidx@gmail.com>,
David Gibson <david@gibson.dropbear.id.au>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] About my strnlen patch
Date: Thu, 21 Dec 2017 12:30:12 -0600 [thread overview]
Message-ID: <8bf902fe-1ec9-4845-a072-af2e7da32ed2@redhat.com> (raw)
In-Reply-To: <0B44C3E6-545D-43B1-B124-97BB9D84BA0C@gmail.com>
On 12/21/2017 08:31 AM, Programmingkid wrote:
> Now would be a good time to push the strnlen patch.
No links to the patch? Generally, when pinging a patch, it's best to
reply to the existing thread, or at least provide a URL to the thread,
where the patch was proposed.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
next prev parent reply other threads:[~2017-12-21 18:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-21 14:31 [Qemu-devel] About my strnlen patch Programmingkid
2017-12-21 18:30 ` Eric Blake [this message]
2017-12-21 18:36 ` Programmingkid
2017-12-21 18:40 ` Eric Blake
2017-12-21 19:07 ` Programmingkid
2017-12-21 20:09 ` 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=8bf902fe-1ec9-4845-a072-af2e7da32ed2@redhat.com \
--to=eblake@redhat.com \
--cc=david@gibson.dropbear.id.au \
--cc=programmingkidx@gmail.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).