From mboxrd@z Thu Jan 1 00:00:00 1970 From: Heiko Carstens Subject: Re: [PATCH] KVM: s390: Disable CONFIG_S390_GUEST_OLD_TRANSPORT by default Date: Tue, 26 Sep 2017 12:47:52 +0200 Message-ID: <20170926104752.GB3209@osiris> References: <1506350729-11311-1-git-send-email-thuth@redhat.com> <3c2b8ae8-ca2a-7b26-8ebd-14f14c286529@linux.vnet.ibm.com> <83cacb4a-94b1-c7c2-e50d-70afea5d3e9c@de.ibm.com> <20170926104019.GA3209@osiris> <376655d1-87e3-4187-d2d1-d1f23c02431a@de.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <376655d1-87e3-4187-d2d1-d1f23c02431a@de.ibm.com> Sender: kvm-owner@vger.kernel.org List-Archive: List-Post: To: Christian Borntraeger Cc: Halil Pasic , Thomas Huth , Cornelia Huck , linux-s390@vger.kernel.org, virtualization@lists.linux-foundation.org, kvm@vger.kernel.org List-ID: On Tue, Sep 26, 2017 at 12:41:41PM +0200, Christian Borntraeger wrote: > > > On 09/26/2017 12:40 PM, Heiko Carstens wrote: > > On Mon, Sep 25, 2017 at 08:37:36PM +0200, Christian Borntraeger wrote: > >> > >> On 09/25/2017 07:54 PM, Halil Pasic wrote: > >>> > >>> > >>> 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 > >>> > >>> 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. > >> > >> FWIW as the original author of that transport > >> Acked-by: Christian Borntraeger > >> > >> I can pick this up for Martins/Heikos tree if you want. > > > > When will this code be removed? > > > > When the config option was initially added Conny said it should survive > > "probably two kernel releases or so, depending on feedback". > > It was merged for v4.8. Now we are five kernel releases later... > > Lets wait for one release and then get rid of it? So it's going to be removed with the next merge window. Where is the patch? ;)