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 Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 3C26FC433EF for ; Fri, 28 Jan 2022 19:18:00 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1344167AbiA1TR7 (ORCPT ); Fri, 28 Jan 2022 14:17:59 -0500 Received: from mxout02.lancloud.ru ([45.84.86.82]:34924 "EHLO mxout02.lancloud.ru" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229702AbiA1TR7 (ORCPT ); Fri, 28 Jan 2022 14:17:59 -0500 Received: from LanCloud DKIM-Filter: OpenDKIM Filter v2.11.0 mxout02.lancloud.ru 01DD42078EC3 Received: from LanCloud Received: from LanCloud Received: from LanCloud Subject: Re: [PATCH 1/2] edac: altera: fix deferred probing To: Borislav Petkov CC: Dinh Nguyen , Mauro Carvalho Chehab , Tony Luck , James Morse , Robert Richter , References: <20220124185503.6720-1-s.shtylyov@omp.ru> <20220124185503.6720-2-s.shtylyov@omp.ru> <7b964ac0-6356-9330-a745-b43e620d051b@kernel.org> <9f28d2de-5119-a7a6-9da7-08b2ce13f1a0@omp.ru> From: Sergey Shtylyov Organization: Open Mobile Platform Message-ID: <5bd9cbc1-12d2-aedc-6d64-ac9eaa2460b1@omp.ru> Date: Fri, 28 Jan 2022 22:17:55 +0300 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.10.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset="utf-8" Content-Language: en-US Content-Transfer-Encoding: 7bit X-Originating-IP: [192.168.11.198] X-ClientProxiedBy: LFEXT02.lancloud.ru (fd00:f066::142) To LFEX1907.lancloud.ru (fd00:f066::207) Precedence: bulk List-ID: X-Mailing-List: linux-edac@vger.kernel.org On 1/28/22 10:16 PM, Borislav Petkov wrote: >>> I think the -stable people will pick it up based on the Fixes: tag. > > My last info is that they don't do that yet. My experience tells they do. >> Ah, you were wondering about returing -EPROBE_DEFER? It started to be returned >> by the commit 9ec36cafe43bf835f8f29273597a5b0cbc8267ef several months before that... > > More precisely, I'm wondering after which commit does the deferred > probing code interpret -EPROBE_DEFER properly so that a backport of this > commit would be even worth the trouble? > > Because if we backport it to kernel where there's not even deferred > probing support, then that backport is a waste of time. See my other mail... MBR, Sergey