On 06/02/2015 05:51 AM, Markus Armbruster wrote:
The most confusing part about this is that you have &error_abort almost
everywhere, but the function doesn't actually abort on error, but rather
returns a negative error code and leaves errp alone.
>>>
>>> True. The function contract
Eric Blake writes:
> On 05/29/2015 05:22 AM, Markus Armbruster wrote:
>> Kevin Wolf writes:
>>
>>> Am 28.05.2015 um 14:21 hat Markus Armbruster geschrieben:
Touches vl.c, which gives me pretext to ask Paolo: would you be
willing to take this through your tree? Or should I take it thr
On 05/29/2015 05:22 AM, Markus Armbruster wrote:
> Kevin Wolf writes:
>
>> Am 28.05.2015 um 14:21 hat Markus Armbruster geschrieben:
>>> Touches vl.c, which gives me pretext to ask Paolo: would you be
>>> willing to take this through your tree? Or should I take it through
>>> mine?
>>
>> After t
Am 29.05.2015 um 13:22 hat Markus Armbruster geschrieben:
> Kevin Wolf writes:
>
> > Am 28.05.2015 um 14:21 hat Markus Armbruster geschrieben:
> >> Touches vl.c, which gives me pretext to ask Paolo: would you be
> >> willing to take this through your tree? Or should I take it through
> >> mine?
Kevin Wolf writes:
> Am 28.05.2015 um 14:21 hat Markus Armbruster geschrieben:
>> Touches vl.c, which gives me pretext to ask Paolo: would you be
>> willing to take this through your tree? Or should I take it through
>> mine?
>
> After this series we have an ugly half-converted state where
> qem
Am 28.05.2015 um 14:21 hat Markus Armbruster geschrieben:
> Touches vl.c, which gives me pretext to ask Paolo: would you be
> willing to take this through your tree? Or should I take it through
> mine?
After this series we have an ugly half-converted state where
qemu_opts_foreach() has both a ret
Touches vl.c, which gives me pretext to ask Paolo: would you be
willing to take this through your tree? Or should I take it through
mine?
Markus Armbruster (9):
vl: Report failure to sandbox at most once
vl: Print -device help at most once
vl: Fail right after first bad -object
QemuOpts:
