| commit | d0e46a55776a59c8fdbb75620e7c5fcf0d6aa029 | |
| author | Max Reitz <mreitz@redhat.com> | |
| Wed, 16 Mar 2016 18:54:34 +0000 (16 19:54 +0100) | ||
| committer | Kevin Wolf <kwolf@redhat.com> | |
| Thu, 17 Mar 2016 14:47:56 +0000 (17 15:47 +0100) | ||
| tree | 56d1064faabd763b05d6acd87c3e9b7a657ced38 | treesnapshot (tar.gz zip) |
| parent | a55448b3681a880b77eaefe8b2c42912000cb481 | commitdiff |
block: Drop BB name from bad option error
The information which BB is concerned does not seem useful enough to
justify its existence in most other place (which may be related to qemu
printing the -drive parameter in question anyway, and for blockdev-add
the attribution is naturally unambiguous). Furthermore, as of a future
patch, bdrv_get_device_name(bs) will always return the empty string
before bdrv_open_inherit() returns.
Therefore, just dropping that information seems to be the best course of
action.
Signed-off-by: Max Reitz <mreitz@redhat.com>
Signed-off-by: Kevin Wolf <kwolf@redhat.com>
The information which BB is concerned does not seem useful enough to
justify its existence in most other place (which may be related to qemu
printing the -drive parameter in question anyway, and for blockdev-add
the attribution is naturally unambiguous). Furthermore, as of a future
patch, bdrv_get_device_name(bs) will always return the empty string
before bdrv_open_inherit() returns.
Therefore, just dropping that information seems to be the best course of
action.
Signed-off-by: Max Reitz <mreitz@redhat.com>
Signed-off-by: Kevin Wolf <kwolf@redhat.com>
| block.c | diffblobblamehistory | |
| tests/qemu-iotests/051.out | diffblobblamehistory | |
| tests/qemu-iotests/051.pc.out | diffblobblamehistory |