On Mon, 2 Dec 2019 17:40:07 +0100
Cornelia Huck <coh...@redhat.com> wrote:

> On Sat, 30 Nov 2019 20:42:39 +0100
> Markus Armbruster <arm...@redhat.com> wrote:
> 
> > Cc: Halil Pasic <pa...@linux.ibm.com>
> > Cc: Cornelia Huck <coh...@redhat.com>
> > Cc: Christian Borntraeger <borntrae...@de.ibm.com>
> > Signed-off-by: Markus Armbruster <arm...@redhat.com>
> > ---
> >  hw/intc/s390_flic_kvm.c | 10 ++++------
> >  1 file changed, 4 insertions(+), 6 deletions(-)
> 
> Reviewed-by: Cornelia Huck <coh...@redhat.com>
> 
> ...someone else wants to take a look before I queue this?
> 

I guess it is a matter of taste.

Acked-by: Halil Pasic <pa...@linux.ibm.com>

The only difference I can see is if the **errp argument where
to already contain an error (*errp). I guess the old code would
just keep the first error, and discard the next one, while error_setv()
does an assert(*errp == NULL).

I assume calling with *errp != NULL is not a valid scenario. But then, I
can't say I understand the use-case behind this discard the newer error
behavior of error_propagate().

Regards,
Halil


Reply via email to