From: Gleb Natapov <gleb@redhat.com>
To: Takuya Yoshikawa <yoshikawa_takuya_b1@lab.ntt.co.jp>
Cc: mtosatti@redhat.com, kvm@vger.kernel.org, agraf@suse.de,
borntraeger@de.ibm.com, cornelia.huck@de.ibm.com,
cdall@cs.columbia.edu
Subject: Re: [PATCH 0/6] KVM: Clean up and optimize set_memory_region() - part2
Date: Thu, 28 Feb 2013 11:18:18 +0200 [thread overview]
Message-ID: <20130228091818.GU23616@redhat.com> (raw)
In-Reply-To: <20130228100213.a71602b6.yoshikawa_takuya_b1@lab.ntt.co.jp>
On Thu, Feb 28, 2013 at 10:02:13AM +0900, Takuya Yoshikawa wrote:
> [ Resending since my email client seemed to fail. ]
>
> On Wed, 27 Feb 2013 18:23:45 +0200
> Gleb Natapov <gleb@redhat.com> wrote:
>
> > On Wed, Feb 27, 2013 at 07:41:03PM +0900, Takuya Yoshikawa wrote:
> > > Note: this is based on the latest master branch.
> > >
> > > I'm sending this before 3.9-rc1 is released since this can cause extra
> > > conflicts unless we make this available to all arch before we start
> > > adding new stuff.
> > >
> > I do not quite sure what you want me to do. Why can't this wait for
> > 3.10?
>
> Sorry for my confusing explanation. This is exactly for 3.10.
>
> I'd like to let the maintainers of arch code know the plan and make them
> prepared for the possible changes for the next development cycle.
>
> It would be nice if this won't make it difficult to sync later: people
> tend to queue up their own code soon.
>
Make perfect sense. Will be applied after -rc1 is released. At this
point master will be merged to next/queue development branches.
--
Gleb.
next prev parent reply other threads:[~2013-02-28 9:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-27 10:41 [PATCH 0/6] KVM: Clean up and optimize set_memory_region() - part2 Takuya Yoshikawa
2013-02-27 10:41 ` [PATCH 1/6] KVM: set_memory_region: Drop user_alloc from prepare/commit_memory_region() Takuya Yoshikawa
2013-02-27 10:43 ` [PATCH 2/6] KVM: set_memory_region: Drop user_alloc from set_memory_region() Takuya Yoshikawa
2013-02-27 10:43 ` [PATCH 3/6] KVM: set_memory_region: Make kvm_mr_change available to arch code Takuya Yoshikawa
2013-02-27 10:44 ` [PATCH 4/6] KVM: set_memory_region: Refactor prepare_memory_region() Takuya Yoshikawa
2013-02-27 10:45 ` [PATCH 5/6] KVM: set_memory_region: Refactor commit_memory_region() Takuya Yoshikawa
2013-02-27 10:46 ` [PATCH 6/6] KVM: ARM: Remove kvm_arch_set_memory_region() Takuya Yoshikawa
2013-02-27 16:23 ` [PATCH 0/6] KVM: Clean up and optimize set_memory_region() - part2 Gleb Natapov
2013-02-28 0:43 ` Takuya Yoshikawa
2013-02-28 1:02 ` Takuya Yoshikawa
2013-02-28 9:18 ` Gleb Natapov [this message]
2013-02-28 1:03 ` Marcelo Tosatti
2013-02-28 9:48 ` Cornelia Huck
2013-03-04 23:22 ` Marcelo Tosatti
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=20130228091818.GU23616@redhat.com \
--to=gleb@redhat.com \
--cc=agraf@suse.de \
--cc=borntraeger@de.ibm.com \
--cc=cdall@cs.columbia.edu \
--cc=cornelia.huck@de.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=yoshikawa_takuya_b1@lab.ntt.co.jp \
/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.