From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.5 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_PASS, USER_AGENT_MUTT autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 42D76C10F14 for ; Tue, 23 Apr 2019 12:34:17 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 0769B204EC for ; Tue, 23 Apr 2019 12:34:17 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1556022857; bh=XuBguYxBfVg7EkKm04mlCyit9mGt2qYdeBYUFWTFsZo=; h=Date:From:To:Cc:Subject:References:In-Reply-To:List-ID:From; b=s4iPffEPgN0od9NC9kwL4E99+ShCFSgES64qX389j1PI2VvuHYjeKnuVc65fd17rM oiV0MBEZOSyVLk8xUDh/8dshNm2dyBPeASwRZmR/AfforVtDbRsxHSCyv6vnOMtZeW qhaEdM1JVmlFkE9liYrAAMqmhRJgdvWWWiWcLObM= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727656AbfDWMeQ (ORCPT ); Tue, 23 Apr 2019 08:34:16 -0400 Received: from mail.kernel.org ([198.145.29.99]:52992 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726033AbfDWMeQ (ORCPT ); Tue, 23 Apr 2019 08:34:16 -0400 Received: from localhost (62-193-50-229.as16211.net [62.193.50.229]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 4F615204EC; Tue, 23 Apr 2019 12:34:15 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1556022855; bh=XuBguYxBfVg7EkKm04mlCyit9mGt2qYdeBYUFWTFsZo=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=AQcMD301uxOz9gJTFX0FidDlMTtp1CGNRmDV/1nwvCHW3hqaCBWngWm8VlhgiDJZ4 +ydWLiSiMuk7n9HP5WRKyKKIf77aLuIiz7WCFqwP0ChaLl8BUuMvkmn/wj7hgI06C/ HGy/z2lfVbey/VjnoMRNeAXmKO4+Kaim3cQt4x30= Date: Tue, 23 Apr 2019 14:34:12 +0200 From: Greg KH To: Kaiyen Chang Cc: stable@vger.kernel.org, adrian.hunter@intel.com, ulf.hansson@linaro.org Subject: Re: [PATCH v1] mmc: sdhci: Handle auto-command errors Message-ID: <20190423123412.GA4129@kroah.com> References: <1556009458-23385-1-git-send-email-kaiyen.chang@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1556009458-23385-1-git-send-email-kaiyen.chang@intel.com> User-Agent: Mutt/1.11.4 (2019-03-13) Sender: stable-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: stable@vger.kernel.org On Tue, Apr 23, 2019 at 04:50:58PM +0800, Kaiyen Chang wrote: > Existing data command CRC error handling on kernel 4.20 stable branch > is non-standard and does not work with some Intel host controllers. > Specifically, the assumption that the host controller will continue > operating normally after the error interrupt, is not valid. So we > suggest cherry-pick the 3 patches listed below to kernel 4.20 stable > branch, which can change the driver to handle the error in the same > manner as a data CRC error. > > 4bf7809: mmc: sdhci: Fix data command CRC error handling > 869f8a6: mmc: sdhci: Rename SDHCI_ACMD12_ERR and SDHCI_INT_ACMD12ERR > af849c8: mmc: sdhci: Handle auto-command errors > > All of the patches above have landed on kernel 5.0 stable branch. The 4.20.y stable branch is long end-of-life, so there is nothing to be able to apply any patch to, sorry. Remember to always check the front page of kernel.org for what trees are still active. greg k-h