From: Wei Yang <richardw.yang@linux.intel.com>
To: Wei Yang <richardw.yang@linux.intel.com>
Cc: qemu-devel@nongnu.org, dgilbert@redhat.com, quintela@redhat.com
Subject: Re: [Qemu-devel] [PATCH 0/4] Multifd Cleanup
Date: Tue, 4 Jun 2019 10:25:07 +0800 [thread overview]
Message-ID: <20190604022507.GA25530@richard> (raw)
In-Reply-To: <20190528014703.21030-1-richardw.yang@linux.intel.com>
Hi, David
Do you prefer I resend 3/4 or it is ok for you to pick up here directly?
On Tue, May 28, 2019 at 09:46:59AM +0800, Wei Yang wrote:
>Just found several small places for unused variables.
>
>Wei Yang (4):
> migration: multifd_save_setup always return 0
> migration/ram.c: use same type in MultiFDPages_t to define offsest
> migration/ram.c: MultiFDSendParams.sem_sync is not really used
> migration/ram.c: multifd_send_state->count is not really used
>
> migration/migration.c | 7 +------
> migration/ram.c | 11 +----------
> 2 files changed, 2 insertions(+), 16 deletions(-)
>
>--
>2.19.1
--
Wei Yang
Help you, Help me
prev parent reply other threads:[~2019-06-04 2:26 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-28 1:46 [Qemu-devel] [PATCH 0/4] Multifd Cleanup Wei Yang
2019-05-28 1:47 ` [Qemu-devel] [PATCH 1/4] migration: multifd_save_setup always return 0 Wei Yang
2019-05-28 8:11 ` Juan Quintela
2019-05-29 0:34 ` Wei Yang
2019-05-29 8:22 ` Juan Quintela
2019-05-29 8:22 ` Juan Quintela
2019-05-28 1:47 ` [Qemu-devel] [PATCH 2/4] migration/ram.c: use same type in MultiFDPages_t to define offsest Wei Yang
2019-05-28 8:12 ` Juan Quintela
2019-05-29 0:34 ` Wei Yang
2019-05-28 1:47 ` [Qemu-devel] [PATCH 3/4] migration/ram.c: MultiFDSendParams.sem_sync is not really used Wei Yang
2019-05-28 8:16 ` Juan Quintela
2019-05-29 0:40 ` Wei Yang
2019-05-28 1:47 ` [Qemu-devel] [PATCH 4/4] migration/ram.c: multifd_send_state->count " Wei Yang
2019-05-28 8:19 ` Juan Quintela
2019-06-04 2:25 ` Wei Yang [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=20190604022507.GA25530@richard \
--to=richardw.yang@linux.intel.com \
--cc=dgilbert@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.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 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.