| commit | 967e3889874b1116090a60c0cb43157130bdbd16 | |
| author | Fabiano Rosas <farosas@suse.de> | |
| Thu, 12 Oct 2023 13:43:43 +0000 (12 10:43 -0300) | ||
| committer | Juan Quintela <quintela@redhat.com> | |
| Tue, 17 Oct 2023 07:25:14 +0000 (17 09:25 +0200) | ||
| tree | 6b4831de22ad6d8f884073bd985889c34ddb26d3 | treesnapshot (tar.gz zip) |
| parent | ee8a7c9c46b8f06969a975ac3fd3fd30491611a7 | commitdiff |
migration/multifd: Clarify Error usage in multifd_channel_connect
The function is currently called from two sites, one always gives it a
NULL Error and the other always gives it a non-NULL Error.
In the non-NULL case, all it does it trace the error and return. One
of the callers already have tracing, add a tracepoint to the other and
stop passing the error into the function.
Cc: Markus Armbruster <armbru@redhat.com>
Signed-off-by: Fabiano Rosas <farosas@suse.de>
Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>
Reviewed-by: Juan Quintela <quintela@redhat.com>
Signed-off-by: Juan Quintela <quintela@redhat.com>
Message-ID: <20231012134343.23757-4-farosas@suse.de>
The function is currently called from two sites, one always gives it a
NULL Error and the other always gives it a non-NULL Error.
In the non-NULL case, all it does it trace the error and return. One
of the callers already have tracing, add a tracepoint to the other and
stop passing the error into the function.
Cc: Markus Armbruster <armbru@redhat.com>
Signed-off-by: Fabiano Rosas <farosas@suse.de>
Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>
Reviewed-by: Juan Quintela <quintela@redhat.com>
Signed-off-by: Juan Quintela <quintela@redhat.com>
Message-ID: <20231012134343.23757-4-farosas@suse.de>
| migration/multifd.c | diffblobblamehistory | |
| migration/trace-events | diffblobblamehistory |