Received: by 2002:a25:8b91:0:0:0:0:0 with SMTP id j17csp5800937ybl; Tue, 10 Dec 2019 11:42:15 -0800 (PST) X-Google-Smtp-Source: APXvYqyjHR8b7+Dz8Xw0XeC3PA8MVVHOHFjuRrsnIs+iiPiEZqmvk7ZFTQJMViQvekmkQtU/iTIs X-Received: by 2002:a9d:7a4b:: with SMTP id z11mr27253092otm.46.1576006934841; Tue, 10 Dec 2019 11:42:14 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1576006934; cv=none; d=google.com; s=arc-20160816; b=O8z+Cbm2Vi6aebN93KxeylfCGG7q8AifGc46jweOr3auXhC+DzpqOONSoSlk93zp4U HHo4n+F1ujbEFS7OCyiUl2fgxeNevoInVOX+yMv4a+JtWc4jKct5iZl8mqSpRICScQIc kWsXaGlfS2frRGZMADkIxQE/nvyGxTmiAhn1jSkD2Ssc/OLaWG5pb4733Y2XdAlUiQ90 XO5cBGx1FcsCld9+SibjkiE905yT86wTStQ6YtPA30AleFt1v1EikOFL+WjmUYqwkhUt haurI4kwc1Y3AEXJ1VpaAxXo0eftkiktyngdVkjs51RH37nzMEtlt1c69nbmVCm3kECx a4NQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=Y6s1QqW+IVCinzvQj1Zp9lAORP9rzs/RfwpMngEWumY=; b=KZXrv5td++fvPO35obcYcMD4yvwr/psVrZr7TKtiEGmqUVUGTA+yDBvdGE98B8UWIz pMq4exwNLpKAFWO7ugaSdipmtfJhjWjD0Ng7JXFIXkpG/LQh3ecAh3gdOCrFnpRhDO5x Y+7TRPPyEjPSGcmYsnXhzePgpQ5fgIdN90aF5ruudi4JdiEz0V3hmUCAQsYACLpwlTZS 1cdLN8ob631ZDe/OQbKJluaaPukqyPznRR3epIvH/VEoQG1RQ1+aYKHiUR599K6hCHQU nksVF/w68J7570p6SrXPVJkmumYy+Fgt6I4wJ1w3cEkcR+7Tfl4VGqXiM0MpUeLkspXP VbSw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=iki.fi Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id x2si2417797otk.66.2019.12.10.11.42.03; Tue, 10 Dec 2019 11:42:14 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=iki.fi Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726741AbfLJTlZ (ORCPT + 99 others); Tue, 10 Dec 2019 14:41:25 -0500 Received: from emh06.mail.saunalahti.fi ([62.142.5.116]:38726 "EHLO emh06.mail.saunalahti.fi" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726018AbfLJTlZ (ORCPT ); Tue, 10 Dec 2019 14:41:25 -0500 X-Greylist: delayed 568 seconds by postgrey-1.27 at vger.kernel.org; Tue, 10 Dec 2019 14:41:24 EST Received: from darkstar.musicnaut.iki.fi (85-76-143-83-nat.elisa-mobile.fi [85.76.143.83]) by emh06.mail.saunalahti.fi (Postfix) with ESMTP id 7D47230056; Tue, 10 Dec 2019 21:31:54 +0200 (EET) Date: Tue, 10 Dec 2019 21:31:54 +0200 From: Aaro Koskinen To: Greg Kroah-Hartman Cc: devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org, David Daney , Nishka Dasgupta , Himadri Pandya , "Frank A. Cancio Bello" , Sumit Pundir , Laura Lazzati Subject: Re: [PATCH 2/2] staging: octeon-usb: delete the octeon usb host controller driver Message-ID: <20191210193153.GB18225@darkstar.musicnaut.iki.fi> References: <20191210091509.3546251-1-gregkh@linuxfoundation.org> <20191210091509.3546251-2-gregkh@linuxfoundation.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20191210091509.3546251-2-gregkh@linuxfoundation.org> User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi, On Tue, Dec 10, 2019 at 10:15:09AM +0100, Greg Kroah-Hartman wrote: > This driver was merged back in 2013 and shows no progress toward every > being merged into the "correct" part of the kernel. Do you mean all the patches since 2013 were "no progress"? Thanks. > The code doesn't even build for anyone unless you have the specific > hardware platform selected, so odds are it doesn't even work anymore. I used it in production almost a decade with no issues with unpatched mainline kernel. All reported issues were fixed. Last kernel I ran was v5.3. > Remove it for now and is someone comes along that has the hardware and > is willing to fix it up, it can be reverted. Probably the next one who tries it, should try add support in dwc2. Originally the maintainer of that driver did not prefer this, maybe the current one does not mind... A.