From: yuchenlin <yuchen...@synology.com>
The CONFIG_VDI_WRITE is here when the first time vdi is added.
But there is no reason to leave an always on and cannot configure option
in the code-side.
Signed-off-by: yuchenlin <yuchen...@synology.com>
---
block/vdi.c | 5 -----
1 file changed, 5 deletions(-)
diff --git a/block/vdi.c b/block/vdi.c
index 6555cffb88..12f92e7891 100644
--- a/block/vdi.c
+++ b/block/vdi.c
@@ -70,9 +70,6 @@
/* Enable debug messages. */
//~ #define CONFIG_VDI_DEBUG
-/* Support write operations on VDI images. */
-#define CONFIG_VDI_WRITE
-
/* Support non-standard block (cluster) size. This is untested.
* Maybe it will be needed for very large images.
*/
@@ -1016,9 +1013,7 @@ static BlockDriver bdrv_vdi = {
.bdrv_make_empty = vdi_make_empty,
.bdrv_co_preadv = vdi_co_preadv,
-#if defined(CONFIG_VDI_WRITE)
.bdrv_co_pwritev = vdi_co_pwritev,
-#endif
.bdrv_get_info = vdi_get_info,
--
2.17.0
