From: Christoph Hellwig <hch@infradead.org>
To: Jason Wang <jasowang@redhat.com>
Cc: Anders Roxell <anders.roxell@linaro.org>,
Arnd Bergmann <arnd@arndb.de>,
mst@redhat.com, linux-kernel@vger.kernel.org,
virtualization@lists.linux-foundation.org,
Guenter Roeck <linux@roeck-us.net>
Subject: Re: [PATCH] virtio: don't prompt CONFIG_VIRTIO_PCI_MODERN
Date: Fri, 19 Feb 2021 10:13:21 +0000 [thread overview]
Message-ID: <20210219101321.GA651861@infradead.org> (raw)
In-Reply-To: <20210219084509.48269-1-jasowang@redhat.com>
On Fri, Feb 19, 2021 at 03:45:09AM -0500, Jason Wang wrote:
> We used to prompt CONFIG_VIRTIO_PCI_MODERN to user which may bring a
> lot of confusion. E.g it may break various default configs which want
> virtio devices.
>
> So this patch fixes this by hide the prompot and document the
> dependency.
Is there any good reason to keep the symbol at all?
_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@infradead.org>
To: Jason Wang <jasowang@redhat.com>
Cc: mst@redhat.com, virtualization@lists.linux-foundation.org,
linux-kernel@vger.kernel.org, Arnd Bergmann <arnd@arndb.de>,
Anders Roxell <anders.roxell@linaro.org>,
Guenter Roeck <linux@roeck-us.net>
Subject: Re: [PATCH] virtio: don't prompt CONFIG_VIRTIO_PCI_MODERN
Date: Fri, 19 Feb 2021 10:13:21 +0000 [thread overview]
Message-ID: <20210219101321.GA651861@infradead.org> (raw)
In-Reply-To: <20210219084509.48269-1-jasowang@redhat.com>
On Fri, Feb 19, 2021 at 03:45:09AM -0500, Jason Wang wrote:
> We used to prompt CONFIG_VIRTIO_PCI_MODERN to user which may bring a
> lot of confusion. E.g it may break various default configs which want
> virtio devices.
>
> So this patch fixes this by hide the prompot and document the
> dependency.
Is there any good reason to keep the symbol at all?
next prev parent reply other threads:[~2021-02-19 10:14 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-19 8:45 [PATCH] virtio: don't prompt CONFIG_VIRTIO_PCI_MODERN Jason Wang
2021-02-19 8:45 ` Jason Wang
2021-02-19 10:12 ` Arnd Bergmann
2021-02-22 3:41 ` Jason Wang
2021-02-22 3:41 ` Jason Wang
2021-02-19 10:13 ` Christoph Hellwig [this message]
2021-02-19 10:13 ` Christoph Hellwig
2021-02-20 1:51 ` Jason Wang
2021-02-20 1:51 ` Jason Wang
2021-02-19 15:38 ` Guenter Roeck
2021-02-19 15:38 ` Guenter Roeck
2021-02-22 3:42 ` Jason Wang
2021-02-22 3:42 ` Jason Wang
2021-02-22 7:29 ` Michael S. Tsirkin
2021-02-22 7:29 ` Michael S. Tsirkin
2021-02-22 9:06 ` Jason Wang
2021-02-22 9:06 ` Jason Wang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210219101321.GA651861@infradead.org \
--to=hch@infradead.org \
--cc=anders.roxell@linaro.org \
--cc=arnd@arndb.de \
--cc=jasowang@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=mst@redhat.com \
--cc=virtualization@lists.linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.