On 25.02.22 12:48, Michael S. Tsirkin wrote:> There's no special reason why virtio-mem needs a default that's
> different from what kconfig provides, any more than e.g. virtio blk.
>
> Signed-off-by: Michael S. Tsirkin <mst at redhat.com>
> ---
> drivers/virtio/Kconfig | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/drivers/virtio/Kconfig b/drivers/virtio/Kconfig
> index 34f80b7a8a64..492fc26f0b65 100644
> --- a/drivers/virtio/Kconfig
> +++ b/drivers/virtio/Kconfig
> @@ -105,7 +105,6 @@ config VIRTIO_BALLOON
>
> config VIRTIO_MEM
> tristate "Virtio mem driver"
> - default m
> depends on X86_64
> depends on VIRTIO
> depends on MEMORY_HOTPLUG
Yeah, why not
Acked-by: David Hildenbrand <david at redhat.com>
--
Thanks,
David / dhildenb