From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: "Philippe Mathieu-Daudé" <philmd@redhat.com>
Cc: Fei Li <shirley17fei@gmail.com>, Fei Li <lifei1214@126.com>,
Juan Quintela <quintela@redhat.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH for-4.0 0/5] fix some segmentation faults and migration issues
Date: Wed, 16 Jan 2019 15:00:22 +0000 [thread overview]
Message-ID: <20190116150022.GC2351@work-vm> (raw)
In-Reply-To: <c32370f9-41c0-49a2-920f-e7cc984237cd@redhat.com>
* Philippe Mathieu-Daudé (philmd@redhat.com) wrote:
> On 1/16/19 5:50 AM, Fei Li wrote:
> > Hi all,
> >
> > Kindly ping. :)
> >
> > As my v10 of qemu_thread_create partly rely on this patch series, I'd
> > like to know
> > when will these 5 patches be merged, or I join them with v10 of
> > qemu_thread_create
> > and send together. Could anyone shed light on me? Thanks for the advice
> > in advance.
>
> This series would get merged quicker if you include the maintainers :)
>
> $ ./scripts/get_maintainer.pl -f migration/*
> Juan Quintela <quintela@redhat.com> (maintainer:Migration)
> "Dr. David Alan Gilbert" <dgilbert@redhat.com> (maintainer:Migration)
>
> Doing that for you by responding to this mail.
We can do it via migration now the set is complete.
Dave
>
> Regards,
>
> Phil.
>
> >
> >
> > Have a nice day
> > Fei
> > 在 2019/1/13 下午10:08, Fei Li 写道:
> >> All these five patches have gotten the Reviewed-by: the first patch
> >> is to fix one segmentation fault and the other four are to fix some
> >> migration issues.
> >>
> >> To be more detail, they are extracted from previous
> >> "[PATCH for-4.0 v9 16/16] qemu_thread_create: propagate errors to
> >> callers to handle.", but actually these five patches are derivative
> >> and not relevant to the mentioned qemu_thread_create patch series.
> >> Thus send them separately to make them be merged earlier.
> >>
> >> Fei Li (5):
> >> Fix segmentation fault when qemu_signal_init fails
> >> migration: fix the multifd code when receiving less channels
> >> migration: multifd_save_cleanup() can't fail, simplify
> >> migration: add more error handling for postcopy_ram_enable_notify
> >> migration: unify error handling for process_incoming_migration_co
> >>
> >> migration/channel.c | 11 ++++++-----
> >> migration/migration.c | 40 +++++++++++++++++++++-------------------
> >> migration/migration.h | 2 +-
> >> migration/postcopy-ram.c | 1 +
> >> migration/ram.c | 28 ++++++++++++++++++----------
> >> migration/ram.h | 4 ++--
> >> migration/savevm.c | 1 +
> >> util/main-loop.c | 8 ++++----
> >> 8 files changed, 54 insertions(+), 41 deletions(-)
> >>
> >
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
next prev parent reply other threads:[~2019-01-16 15:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-13 14:08 [Qemu-devel] [PATCH for-4.0 0/5] fix some segmentation faults and migration issues Fei Li
2019-01-13 14:08 ` [Qemu-devel] [PATCH for-4.0 1/5] Fix segmentation fault when qemu_signal_init fails Fei Li
2019-01-13 14:08 ` [Qemu-devel] [PATCH for-4.0 2/5] migration: fix the multifd code when receiving less channels Fei Li
2019-01-13 14:08 ` [Qemu-devel] [PATCH for-4.0 3/5] migration: multifd_save_cleanup() can't fail, simplify Fei Li
2019-01-13 14:08 ` [Qemu-devel] [PATCH for-4.0 4/5] migration: add more error handling for postcopy_ram_enable_notify Fei Li
2019-01-13 14:08 ` [Qemu-devel] [PATCH for-4.0 5/5] migration: unify error handling for process_incoming_migration_co Fei Li
2019-01-16 4:50 ` [Qemu-devel] [PATCH for-4.0 0/5] fix some segmentation faults and migration issues Fei Li
2019-01-16 14:52 ` Philippe Mathieu-Daudé
2019-01-16 15:00 ` Dr. David Alan Gilbert [this message]
2019-01-17 2:04 ` fei
2019-01-23 11:34 ` Dr. David Alan Gilbert
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=20190116150022.GC2351@work-vm \
--to=dgilbert@redhat.com \
--cc=lifei1214@126.com \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=shirley17fei@gmail.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;
as well as URLs for NNTP newsgroup(s).