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.6 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,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 85862C10F14 for ; Tue, 23 Apr 2019 13:42:56 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 4CF5220693 for ; Tue, 23 Apr 2019 13:42:56 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1556026976; bh=vTnFIosHt9GsbxYkbcyrcPFcc4kpL4noWvnudOxICHU=; h=Date:From:To:Cc:Subject:References:In-Reply-To:List-ID:From; b=k7/s8QDahkgi3pxurYkvNdKL6WbFybjHj8O9SUrVNAsLE5YTfOLmlFwRy9zfhoJT5 /NT9HnC9P4ePBOGuwQUIj20AqqxX55yS0DUUYJwvPNiVcIyAflbMabyQyYO/9365qq QQbEQskmNwh5B4Ky9bpBhKoP0khwSKoWY8fCztEo= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727761AbfDWNm4 (ORCPT ); Tue, 23 Apr 2019 09:42:56 -0400 Received: from mail.kernel.org ([198.145.29.99]:32800 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726659AbfDWNmz (ORCPT ); Tue, 23 Apr 2019 09:42:55 -0400 Received: from localhost (c-73-47-72-35.hsd1.nh.comcast.net [73.47.72.35]) (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 ED18F20693; Tue, 23 Apr 2019 13:42:54 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1556026975; bh=vTnFIosHt9GsbxYkbcyrcPFcc4kpL4noWvnudOxICHU=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=cFSOfI2fT3y5oI7V6pZG1DlyfMcC1Kx/RpwJZ2xSQnEC0pYA9UG/74L11O/pMv3OH JVKAXvY4XT7n27ZQ8u0kgY0KKzvkMjQJQre8rOAvPpN+KiFqgUqUxRJNYJm9YHasVZ ZyY3YaKAUYe6X/SRuOel/8DNmGVabQUV96Qw5xjU= Date: Tue, 23 Apr 2019 09:42:53 -0400 From: Sasha Levin 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: <20190423134253.GL17719@sasha-vm> References: <1556009458-23385-1-git-send-email-kaiyen.chang@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: <1556009458-23385-1-git-send-email-kaiyen.chang@intel.com> User-Agent: Mutt/1.10.1 (2018-07-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. 4.20 went EoL quite a while ago, you should be using 5.0 at this point. I've queued these to older stable kernels, thanks. -- Thanks, Sasha