From: Sasha Levin <levinsasha928@gmail.com>
To: Avi Kivity <avi@redhat.com>
Cc: kvm@vger.kernel.org, Marcelo Tosatti <mtosatti@redhat.com>
Subject: Re: [PATCH 1/2] KVM: Use kmemdup() instead of kzalloc/memcpy
Date: Sun, 27 Nov 2011 14:37:05 +0200 [thread overview]
Message-ID: <1322397425.3248.3.camel@lappy> (raw)
In-Reply-To: <4ED22C38.2000902@redhat.com>
On Sun, 2011-11-27 at 14:25 +0200, Avi Kivity wrote:
> On 11/23/2011 05:15 PM, Sasha Levin wrote:
> > Switch to kmemdup() in two places to shorten the code and avoid possible bugs.
> >
>
> Doesn't apply...
>
Needs rebasing due to the memslot patch. I'll resend.
--
Sasha.
prev parent reply other threads:[~2011-11-27 12:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-23 15:15 [PATCH 1/2] KVM: Use kmemdup() instead of kzalloc/memcpy Sasha Levin
2011-11-23 15:15 ` [PATCH 2/2] KVM: Use memdup_user instead of kmalloc/copy_from_user Sasha Levin
2011-11-27 12:25 ` [PATCH 1/2] KVM: Use kmemdup() instead of kzalloc/memcpy Avi Kivity
2011-11-27 12:37 ` Sasha Levin [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=1322397425.3248.3.camel@lappy \
--to=levinsasha928@gmail.com \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--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).