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 rebased 2/2] KVM: Use memdup_user instead of kmalloc/copy_from_user
Date: Wed, 07 Dec 2011 16:47:30 +0200 [thread overview]
Message-ID: <4EDF7C82.3020007@redhat.com> (raw)
In-Reply-To: <1323020189-6616-2-git-send-email-levinsasha928@gmail.com>
On 12/04/2011 07:36 PM, Sasha Levin wrote:
> Switch to using memdup_user when possible. This makes code more
> smaller and compact, and prevents errors.
>
>
Thanks, applied.
--
error compiling committee.c: too many arguments to function
prev parent reply other threads:[~2011-12-07 14:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-04 17:36 [PATCH rebased 1/2] KVM: Use kmemdup() instead of kmalloc/memcpy Sasha Levin
2011-12-04 17:36 ` [PATCH rebased 2/2] KVM: Use memdup_user instead of kmalloc/copy_from_user Sasha Levin
2011-12-07 14:47 ` 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=4EDF7C82.3020007@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.