On 2013/5/7 15:38, Markus Armbruster wrote:
Dong Xu Wang writes:
On 2013/5/6 20:20, Markus Armbruster wrote:
Dong Xu Wang writes:
These functions will be used in next commit. qemu_opt_get_(*)_del functions
are used to make sure we have the same behaviors as before: after get an
option valu
Dong Xu Wang writes:
> On 2013/5/6 20:20, Markus Armbruster wrote:
>> Dong Xu Wang writes:
>>
>>> These functions will be used in next commit. qemu_opt_get_(*)_del functions
>>> are used to make sure we have the same behaviors as before: after get an
>>> option value, options++.
>>
>> I don't un
On 2013/5/6 20:20, Markus Armbruster wrote:
Dong Xu Wang writes:
These functions will be used in next commit. qemu_opt_get_(*)_del functions
are used to make sure we have the same behaviors as before: after get an
option value, options++.
I don't understand the last sentence.
Signed-off-by
Dong Xu Wang writes:
> These functions will be used in next commit. qemu_opt_get_(*)_del functions
> are used to make sure we have the same behaviors as before: after get an
> option value, options++.
I don't understand the last sentence.
> Signed-off-by: Dong Xu Wang
> ---
> include/qemu/opt
These functions will be used in next commit. qemu_opt_get_(*)_del functions
are used to make sure we have the same behaviors as before: after get an
option value, options++.
Signed-off-by: Dong Xu Wang
---
include/qemu/option.h | 11 +-
util/qemu-option.c| 103 ++