drivers/virtio: Clarify CONFIG_VIRTIO_MEM for unsupported architectures
authorDavid Hildenbrand <david@redhat.com>
Fri, 10 Jun 2022 09:47:37 +0000 (11:47 +0200)
committerMichael S. Tsirkin <mst@redhat.com>
Thu, 11 Aug 2022 08:06:38 +0000 (04:06 -0400)
commit0b6fd46ec5f5720b76cbb01300ed9f7b7c6365c4
tree9da799a2f6ac0e30b9c71946506a2e1ce5b91ca1
parent02213273f72a43bad3a8e9c18595a2c74ee487e8
drivers/virtio: Clarify CONFIG_VIRTIO_MEM for unsupported architectures

Let's make it clearer that simply unlocking CONFIG_VIRTIO_MEM on an
architecture is most probably not sufficient to have it working as
expected.

Cc: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Jason Wang <jasowang@redhat.com>
Cc: Gavin Shan <gshan@redhat.com>
Signed-off-by: David Hildenbrand <david@redhat.com>
Message-Id: <20220610094737.65254-1-david@redhat.com>
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
drivers/virtio/Kconfig