From: Eric Blake <eblake@redhat.com>
To: riku.voipio@linaro.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v2 01/13] signal/all: remove __get/__put_user return value reading
Date: Fri, 06 Jun 2014 06:51:50 -0600 [thread overview]
Message-ID: <5391B966.8000008@redhat.com> (raw)
In-Reply-To: <1402048017-30604-2-git-send-email-riku.voipio@linaro.org>
[-- Attachment #1: Type: text/plain, Size: 509 bytes --]
On 06/06/2014 03:46 AM, riku.voipio@linaro.org wrote:
> From: Riku Voipio <riku.voipio@linaro.org>
>
> Remove all the simple cases of reading the return value
> of __get_user and __put_user.
You may want to investigate your patch mail setup. Your threading was
broken - this (and the other 12 patches) should have been in-reply-to
your 0/13 cover letter, rather than top-level threads.
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]
prev parent reply other threads:[~2014-06-06 12:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-06 9:46 [Qemu-devel] [PATCH v2 01/13] signal/all: remove __get/__put_user return value reading riku.voipio
2014-06-06 12:51 ` Eric Blake [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=5391B966.8000008@redhat.com \
--to=eblake@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=riku.voipio@linaro.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).