From: Eric Blake <eblake@redhat.com>
To: Fei Li <fli@suse.com>, Markus Armbruster <armbru@redhat.com>
Cc: David Gibson <dgibson@redhat.com>,
qemu-devel@nongnu.org,
"Dr . David Alan Gilbert" <dgilbert@redhat.com>
Subject: Re: [Qemu-devel] [PATCH for-4.0 v8 6/7] qemu_thread_create: propagate the error to callers to handle
Date: Wed, 19 Dec 2018 11:29:16 -0600 [thread overview]
Message-ID: <9be94c80-623d-c1e7-2524-07b07d05446c@redhat.com> (raw)
In-Reply-To: <cc510f12-e94c-bd90-ce01-4ad5d143420f@suse.com>
On 12/19/18 6:14 AM, Fei Li wrote:
>>>>> 28 files changed, 243 insertions(+), 101 deletions(-)
>> I recommend to split this patch. First part adds the Error ** parameter
>> to qemu_thread_create(), passing &error_abort everywhere. No functional
>> change. Subsequent patches then improve on &error_abort. This way,
>> each improvement patch can be cc'ed to just that part's maintainer(s).
>> Parts you don't want to touch you simply leave at &error_abort. Makes
>> sense?
> Yes, I think this makes sense, much clearer. :) But I am a little
> worried about
> whether too many subsequent improvement patches (some of them are quite
> small changes) are acceptable.
A long series of small patches, where each patch is cc'd to an
appropriate maintainer, will likely get cumulative reviews faster than a
single monolithic patch where no one person is the expert on every line
touched.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
next prev parent reply other threads:[~2018-12-19 17:29 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-11 9:50 [Qemu-devel] [PATCH for-4.0 v8 0/7] qemu_thread_create: propagate errors to callers to check Fei Li
2018-12-11 9:50 ` [Qemu-devel] [PATCH for-4.0 v8 1/7] Fix segmentation fault when qemu_signal_init fails Fei Li
2018-12-11 9:50 ` [Qemu-devel] [PATCH for-4.0 v8 2/7] qemu_init_vcpu: add a new Error parameter to propagate Fei Li
2018-12-11 9:50 ` [Qemu-devel] [PATCH for-4.0 v8 3/7] migration: fix the multifd code when receiving less channels Fei Li
2018-12-13 6:17 ` Markus Armbruster
2018-12-17 11:45 ` Fei Li
2018-12-19 14:11 ` Markus Armbruster
2018-12-20 3:27 ` Fei Li
2018-12-11 9:50 ` [Qemu-devel] [PATCH for-4.0 v8 4/7] migration: remove unused &local_err parameter in multifd_save_cleanup Fei Li
2018-12-11 9:50 ` [Qemu-devel] [PATCH for-4.0 v8 5/7] migration: add more error handling for postcopy_ram_enable_notify Fei Li
2018-12-11 9:50 ` [Qemu-devel] [PATCH for-4.0 v8 6/7] qemu_thread_create: propagate the error to callers to handle Fei Li
2018-12-13 7:26 ` Markus Armbruster
2018-12-14 0:24 ` David Gibson
2018-12-19 9:29 ` Markus Armbruster
2019-01-02 2:29 ` David Gibson
2018-12-17 7:29 ` Fei Li
2018-12-18 12:40 ` Fei Li
2018-12-19 10:11 ` Markus Armbruster
2018-12-19 10:10 ` Markus Armbruster
2018-12-19 12:14 ` Fei Li
2018-12-19 17:29 ` Eric Blake [this message]
2018-12-20 3:20 ` Fei Li
2018-12-21 9:36 ` Fei Li
2018-12-24 3:34 ` Peter Xu
2018-12-24 6:53 ` Fei Li
2018-12-25 12:18 ` Fei Li
2018-12-11 9:50 ` [Qemu-devel] [PATCH for-4.0 v8 7/7] qemu_thread_join: fix segmentation fault Fei Li
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=9be94c80-623d-c1e7-2524-07b07d05446c@redhat.com \
--to=eblake@redhat.com \
--cc=armbru@redhat.com \
--cc=dgibson@redhat.com \
--cc=dgilbert@redhat.com \
--cc=fli@suse.com \
--cc=qemu-devel@nongnu.org \
/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).