From: "Michael R. Hines" <mrhines@linux.vnet.ibm.com>
To: Isaku Yamahata <yamahata@private.email.ne.jp>
Cc: owasserm@redhat.com, quintela@redhat.com, mrhines@us.ibm.com,
qemu-devel@nongnu.org, pbonzini@redhat.com
Subject: Re: [Qemu-devel] [PATCH 1/2] rdma: constify ram_chunk_{index, start, end}
Date: Wed, 18 Sep 2013 10:28:51 -0400 [thread overview]
Message-ID: <5239B8A3.10305@linux.vnet.ibm.com> (raw)
In-Reply-To: <5d53d839653bf4fd24d5cb56f6d24d3dc3f8f8a5.1378261891.git.yamahata@private.email.ne.jp>
On 09/03/2013 10:32 PM, Isaku Yamahata wrote:
> Signed-off-by: Isaku Yamahata <yamahata@private.email.ne.jp>
> ---
> migration-rdma.c | 8 +++++---
> 1 file changed, 5 insertions(+), 3 deletions(-)
>
> diff --git a/migration-rdma.c b/migration-rdma.c
> index e71c10a..db5a908 100644
> --- a/migration-rdma.c
> +++ b/migration-rdma.c
> @@ -511,19 +511,21 @@ static int qemu_rdma_exchange_send(RDMAContext *rdma, RDMAControlHeader *head,
> int *resp_idx,
> int (*callback)(RDMAContext *rdma));
>
> -static inline uint64_t ram_chunk_index(uint8_t *start, uint8_t *host)
> +static inline uint64_t ram_chunk_index(const uint8_t *start,
> + const uint8_t *host)
> {
> return ((uintptr_t) host - (uintptr_t) start) >> RDMA_REG_CHUNK_SHIFT;
> }
>
> -static inline uint8_t *ram_chunk_start(RDMALocalBlock *rdma_ram_block,
> +static inline uint8_t *ram_chunk_start(const RDMALocalBlock *rdma_ram_block,
> uint64_t i)
> {
> return (uint8_t *) (((uintptr_t) rdma_ram_block->local_host_addr)
> + (i << RDMA_REG_CHUNK_SHIFT));
> }
>
> -static inline uint8_t *ram_chunk_end(RDMALocalBlock *rdma_ram_block, uint64_t i)
> +static inline uint8_t *ram_chunk_end(const RDMALocalBlock *rdma_ram_block,
> + uint64_t i)
> {
> uint8_t *result = ram_chunk_start(rdma_ram_block, i) +
> (1UL << RDMA_REG_CHUNK_SHIFT);
Isaku, you are sending lots of "little" patches which may or may not be
properly rebased upon previous patches.
Could you please group your current patch series into a single series with a
descriptive cover letter along with the previous patches?
If you need create a new patch specifically for RDMA before a previous
patch as been applied to my tree, then please include the old one into
the new patch series with a description and a "resend" in the title.
Then I can review them at once apply them all to my tree
so the maintaner has an easier time.
Thanks,
- Michael
next prev parent reply other threads:[~2013-09-18 14:29 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 [this message]
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
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=5239B8A3.10305@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).