qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Michael R. Hines" <mrhines@linux.vnet.ibm.com>
To: quintela@redhat.com
Cc: Isaku Yamahata <yamahata@private.email.ne.jp>,
	owasserm@redhat.com, qemu-devel@nongnu.org, mrhines@us.ibm.com,
	pbonzini@redhat.com
Subject: Re: [Qemu-devel] [PATCH 1/2] rdma: constify ram_chunk_{index, start, end}
Date: Tue, 24 Sep 2013 13:44:38 -0400	[thread overview]
Message-ID: <5241CF86.4020708@linux.vnet.ibm.com> (raw)
In-Reply-To: <87siwup1c4.fsf@elfo.elfo>

On 09/24/2013 01:38 PM, Juan Quintela wrote:
> "Michael R. Hines" <mrhines@linux.vnet.ibm.com> wrote:
>> On 09/24/2013 12:36 PM, Juan Quintela wrote:
>>> "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.
>>>
>> That's a good question - as I'm also new to the maintenance process,
>> what would you recommend?
>>
>> I will definitely be contributing/monitoring/reviewing the RDMA code
>> for the forseeable future....
> I integrate it,  and in migration-rdma.c,  I wait for your nack/ack.
> what do you think?
>
> Later,  Juan.
>
Sounds like a plan. Thank you =)

- Michael

      reply	other threads:[~2013-09-24 17:45 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
2013-09-24 17:21         ` Michael R. Hines
2013-09-24 17:38           ` Juan Quintela
2013-09-24 17:44             ` Michael R. Hines [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=5241CF86.4020708@linux.vnet.ibm.com \
    --to=mrhines@linux.vnet.ibm.com \
    --cc=mrhines@us.ibm.com \
    --cc=owasserm@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@redhat.com \
    --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 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).