From: Juan Quintela <quintela@redhat.com>
To: "Michael R. Hines" <mrhines@linux.vnet.ibm.com>
Cc: Isaku Yamahata <yamahata@private.email.ne.jp>,
owasserm@redhat.com, pbonzini@redhat.com, mrhines@us.ibm.com,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 1/2] rdma: constify ram_chunk_{index, start, end}
Date: Tue, 24 Sep 2013 18:36:53 +0200 [thread overview]
Message-ID: <87wqm6p462.fsf@elfo.elfo> (raw)
In-Reply-To: <523C5779.4010309@linux.vnet.ibm.com> (Michael R. Hines's message of "Fri, 20 Sep 2013 10:11:05 -0400")
"Michael R. Hines" <mrhines@linux.vnet.ibm.com> wrote:
> On 09/20/2013 03:55 AM, Isaku Yamahata wrote:
>> On Wed, Sep 18, 2013 at 10:28:51AM -0400, Michael R. Hines wrote:
>>> On 09/03/2013 10:32 PM, Isaku Yamahata wrote:
>>>> Signed-off-by: Isaku Yamahata <yamahata@private.email.ne.jp>
>
> There's no need to rebase against github or track my branches.
>
> Just use qemu.org master.
Michael, I sent this on my pull request (it was trivial enough).
How do you want to track migration-rdma patches? Should they pass
through you, or should I pick them depending on your Ack/Nack?
Later, Juan.
next prev parent reply other threads:[~2013-09-24 16:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-04 2:32 [Qemu-devel] [PATCH 1/2] rdma: constify ram_chunk_{index, start, end} Isaku Yamahata
2013-09-04 2:32 ` [Qemu-devel] [PATCH 2/2] rdma: simplify qemu_rdma_register_and_get_keys() Isaku Yamahata
2013-09-18 13:00 ` Juan Quintela
2013-09-18 15:01 ` Michael R. Hines
2013-09-20 16:59 ` Isaku Yamahata
2013-09-20 17:44 ` Michael R. Hines
2013-09-18 12:55 ` [Qemu-devel] [PATCH 1/2] rdma: constify ram_chunk_{index, start, end} Juan Quintela
2013-09-18 14:28 ` Michael R. Hines
2013-09-20 7:55 ` Isaku Yamahata
2013-09-20 14:11 ` Michael R. Hines
2013-09-24 16:36 ` Juan Quintela [this message]
2013-09-24 17:21 ` Michael R. Hines
2013-09-24 17:38 ` Juan Quintela
2013-09-24 17:44 ` Michael R. Hines
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=87wqm6p462.fsf@elfo.elfo \
--to=quintela@redhat.com \
--cc=mrhines@linux.vnet.ibm.com \
--cc=mrhines@us.ibm.com \
--cc=owasserm@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=yamahata@private.email.ne.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.