From: Jason Wang <jasowang@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: linux-s390@vger.kernel.org, tsbogend@alpha.franken.de,
gor@linux.ibm.com, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org, heiko.carstens@de.ibm.com,
linux-mips@vger.kernel.org,
virtualization@lists.linux-foundation.org,
borntraeger@de.ibm.com, geert@linux-m68k.org,
netdev@vger.kernel.org, paulus@samba.org,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH V2] vhost: do not enable VHOST_MENU by default
Date: Fri, 17 Apr 2020 17:33:56 +0800 [thread overview]
Message-ID: <ce8a18e5-3c74-73cc-57c5-10c40af838a3@redhat.com> (raw)
In-Reply-To: <20200417050029-mutt-send-email-mst@kernel.org>
On 2020/4/17 下午5:01, Michael S. Tsirkin wrote:
>> There could be some misunderstanding here. I thought it's somehow similar: a
>> CONFIG_VHOST_MENU=y will be left in the defconfigs even if CONFIG_VHOST is
>> not set.
>>
>> Thanks
>>
> BTW do entries with no prompt actually appear in defconfig?
>
Yes. I can see CONFIG_VHOST_DPN=y after make ARCH=m68k defconfig
Thanks
next prev parent reply other threads:[~2020-04-17 9:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-15 2:43 [PATCH V2] vhost: do not enable VHOST_MENU by default Jason Wang
2020-04-16 22:55 ` Michael S. Tsirkin
2020-04-17 3:12 ` Jason Wang
2020-04-17 6:33 ` Michael S. Tsirkin
2020-04-17 7:36 ` Jason Wang
2020-04-17 8:29 ` Michael S. Tsirkin
2020-04-17 8:39 ` Jason Wang
2020-04-17 8:46 ` Michael S. Tsirkin
2020-04-17 8:51 ` Jason Wang
2020-04-17 8:57 ` Michael S. Tsirkin
2020-04-17 9:25 ` Geert Uytterhoeven
2020-04-17 9:32 ` Jason Wang
2020-04-17 9:01 ` Michael S. Tsirkin
2020-04-17 9:33 ` Jason Wang [this message]
2020-04-17 9:38 ` Michael S. Tsirkin
2020-04-17 9:48 ` 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=ce8a18e5-3c74-73cc-57c5-10c40af838a3@redhat.com \
--to=jasowang@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=geert@linux-m68k.org \
--cc=gor@linux.ibm.com \
--cc=heiko.carstens@de.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=paulus@samba.org \
--cc=tsbogend@alpha.franken.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).