From: Halil Pasic <pasic@linux.vnet.ibm.com>
To: Thomas Huth <thuth@redhat.com>, Cornelia Huck <cohuck@redhat.com>
Cc: linux-s390@vger.kernel.org,
virtualization@lists.linux-foundation.org, kvm@vger.kernel.org,
Christian Borntraeger <borntraeger@de.ibm.com>
Subject: Re: [PATCH] KVM: s390: Disable CONFIG_S390_GUEST_OLD_TRANSPORT by default
Date: Mon, 25 Sep 2017 19:54:20 +0200 [thread overview]
Message-ID: <3c2b8ae8-ca2a-7b26-8ebd-14f14c286529@linux.vnet.ibm.com> (raw)
In-Reply-To: <1506350729-11311-1-git-send-email-thuth@redhat.com>
On 09/25/2017 04:45 PM, Thomas Huth wrote:
> There is no recent user space application available anymore which still
> supports this old virtio transport, so let's disable this by default.
>
> Signed-off-by: Thomas Huth <thuth@redhat.com>
I don't have any objections, but there may be something I'm not aware of.
Let's see what Connie says. From my side it's ack.
Via whom is this supposed to go in? Looking at the MAINTAINERS, I would
say Martin or Heiko but I don't see them among the recipients.
Regards,
Halil
> ---
> arch/s390/Kconfig | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/s390/Kconfig b/arch/s390/Kconfig
> index 48af970..923bf04 100644
> --- a/arch/s390/Kconfig
> +++ b/arch/s390/Kconfig
> @@ -930,7 +930,7 @@ config S390_GUEST
> the KVM hypervisor.
>
> config S390_GUEST_OLD_TRANSPORT
> - def_bool y
> + def_bool n
> prompt "Guest support for old s390 virtio transport (DEPRECATED)"
> depends on S390_GUEST
> help
>
next prev parent reply other threads:[~2017-09-25 17:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-25 14:45 [PATCH] KVM: s390: Disable CONFIG_S390_GUEST_OLD_TRANSPORT by default Thomas Huth
2017-09-25 17:54 ` Halil Pasic [this message]
2017-09-25 18:37 ` Christian Borntraeger
2017-09-26 2:44 ` Thomas Huth
2017-09-26 10:40 ` Heiko Carstens
2017-09-26 10:41 ` Christian Borntraeger
2017-09-26 10:47 ` Heiko Carstens
2017-09-26 10:57 ` Thomas Huth
2017-09-26 11:04 ` Heiko Carstens
2017-09-26 11:10 ` Cornelia Huck
2017-09-26 7:33 ` Christian Borntraeger
2017-09-26 7:53 ` Cornelia Huck
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=3c2b8ae8-ca2a-7b26-8ebd-14f14c286529@linux.vnet.ibm.com \
--to=pasic@linux.vnet.ibm.com \
--cc=borntraeger@de.ibm.com \
--cc=cohuck@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=thuth@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox