From: Avi Kivity <avi@redhat.com>
To: Sasha Levin <levinsasha928@gmail.com>
Cc: kvm@vger.kernel.org, Marcelo Tosatti <mtosatti@redhat.com>
Subject: Re: [PATCH v2 1/2] KVM: Use kmemdup() instead of kmalloc/memcpy
Date: Sun, 04 Dec 2011 18:57:45 +0200 [thread overview]
Message-ID: <4EDBA689.6020906@redhat.com> (raw)
In-Reply-To: <1322397797-6465-1-git-send-email-levinsasha928@gmail.com>
On 11/27/2011 02:43 PM, Sasha Levin wrote:
> Switch to kmemdup() in two places to shorten the code and avoid possible bugs.
>
Doesn't apply, please rebase.
--
error compiling committee.c: too many arguments to function
prev parent reply other threads:[~2011-12-04 16:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-27 12:43 [PATCH v2 1/2] KVM: Use kmemdup() instead of kmalloc/memcpy Sasha Levin
2011-11-27 12:43 ` [PATCH v2 2/2] KVM: Use memdup_user instead of kmalloc/copy_from_user Sasha Levin
2011-12-04 16:57 ` Avi Kivity [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=4EDBA689.6020906@redhat.com \
--to=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=levinsasha928@gmail.com \
--cc=mtosatti@redhat.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).