[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <f87db49d-16f7-6607-35ce-9a2a9391c01f@redhat.com>
Date: Fri, 25 Feb 2022 14:30:34 +0100
From: David Hildenbrand <david@...hat.com>
To: "Michael S. Tsirkin" <mst@...hat.com>, linux-kernel@...r.kernel.org
Cc: Jason Wang <jasowang@...hat.com>,
virtualization@...ts.linux-foundation.org
Subject: Re: [PATCH] virtio: drop default for virtio-mem
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@...hat.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@...hat.com>
--
Thanks,
David / dhildenb
Powered by blists - more mailing lists