From: Sasha Levin <sasha.levin@oracle.com>
To: Michel Lespinasse <walken@google.com>
Cc: Sasha Levin <levinsasha928@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
Pekka Enberg <penberg@kernel.org>,
Asias He <asias.hejun@gmail.com>, Ingo Molnar <mingo@elte.hu>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/3] remove kvm's use of augmented rbtree
Date: Mon, 10 Dec 2012 16:57:26 -0500 [thread overview]
Message-ID: <50C65AC6.9050904@oracle.com> (raw)
In-Reply-To: <CANN689Gy3nLBasBea-nqkK7zTC4XuhUKH=FmOTcq_pKWPi_xmw@mail.gmail.com>
On 12/10/2012 04:50 PM, Michel Lespinasse wrote:
> On Mon, Dec 10, 2012 at 8:22 AM, Sasha Levin <levinsasha928@gmail.com> wrote:
>> Ping?
>
> Hey Sasha,
>
> There seems to have been some confusion here. After your last message,
> I expected *you* to take the patches and push them towards kvm tree.
> But, I guess you were waiting for Pekka's reply first ? Or did you
> expect me to go push the patches ?
>
> If it helps, I could push this through Andrew's -mm tree; however I
> think it would make the most sense if these could reach linus's tree
> through a kvm merge rather than through Andrew's -mm...
Ah, no, Pekka is the one taking care of the KVM tools tree, so I'm we're waiting
for him to take a look at the patches and take them if they look fine to him :)
Thanks,
Sasha
next prev parent reply other threads:[~2012-12-10 21:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-25 2:40 Michel Lespinasse
2012-11-25 2:44 ` [PATCH 1/3] kvm: ensure non-overlapping intervals in rb_int_insert() Michel Lespinasse
2012-11-25 2:44 ` [PATCH 2/3] kvm: rb_int_search_single simplification Michel Lespinasse
2012-11-25 2:44 ` [PATCH 3/3] kvm: remove max_high field in rb_int_node structure Michel Lespinasse
2012-11-25 22:14 ` [PATCH 0/3] remove kvm's use of augmented rbtree Sasha Levin
2012-12-10 16:22 ` Sasha Levin
2012-12-10 21:50 ` Michel Lespinasse
2012-12-10 21:57 ` Sasha Levin [this message]
2012-12-11 10:30 ` Pekka Enberg
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=50C65AC6.9050904@oracle.com \
--to=sasha.levin@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=asias.hejun@gmail.com \
--cc=levinsasha928@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=penberg@kernel.org \
--cc=walken@google.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
Powered by JetHome