Re: [PATCH v6 05/12] qmp: Call monitor_set_cur() only in qmp_dispatch()

2020-08-04 Thread Markus Armbruster
Kevin Wolf writes: > The correct way to set the current monitor for a coroutine handler is > different that for a blocking handler, so monitor_set_cur() can only be will be different > called in qmp_dispatch(). needs to be called in > > Signed-off-by: Kevin Wolf > --- > include/qapi/qmp/dis

Re: [PATCH v6 05/12] qmp: Call monitor_set_cur() only in qmp_dispatch()

2020-05-28 Thread Eric Blake
On 5/28/20 10:37 AM, Kevin Wolf wrote: The correct way to set the current monitor for a coroutine handler is different that for a blocking handler, so monitor_set_cur() can only be s/that/than/ called in qmp_dispatch(). Signed-off-by: Kevin Wolf --- include/qapi/qmp/dispatch.h | 3 ++- m

[PATCH v6 05/12] qmp: Call monitor_set_cur() only in qmp_dispatch()

2020-05-28 Thread Kevin Wolf
The correct way to set the current monitor for a coroutine handler is different that for a blocking handler, so monitor_set_cur() can only be called in qmp_dispatch(). Signed-off-by: Kevin Wolf --- include/qapi/qmp/dispatch.h | 3 ++- monitor/qmp.c | 7 +-- qapi/qmp-dispatch.c