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.3 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_PASS,URIBL_BLOCKED,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 61F13ECDFB8 for ; Tue, 17 Jul 2018 22:13:06 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 0E97B2077B for ; Tue, 17 Jul 2018 22:13:06 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 0E97B2077B Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=bootlin.com Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730707AbeGQWrq (ORCPT ); Tue, 17 Jul 2018 18:47:46 -0400 Received: from mail.bootlin.com ([62.4.15.54]:58738 "EHLO mail.bootlin.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729754AbeGQWrq (ORCPT ); Tue, 17 Jul 2018 18:47:46 -0400 Received: by mail.bootlin.com (Postfix, from userid 110) id 881EE206F6; Wed, 18 Jul 2018 00:13:01 +0200 (CEST) Received: from localhost (unknown [88.191.26.124]) by mail.bootlin.com (Postfix) with ESMTPSA id 41619206F3; Wed, 18 Jul 2018 00:13:01 +0200 (CEST) Date: Wed, 18 Jul 2018 00:13:01 +0200 From: Alexandre Belloni To: Andy Shevchenko Cc: Mark Brown , James Hogan , Paul Burton , linux-spi , devicetree , Linux Kernel Mailing List , Linux MIPS Mailing List , Thomas Petazzoni , Allan Nielsen Subject: Re: [PATCH 1/5] spi: dw: fix possible race condition Message-ID: <20180717221301.GF3211@piout.net> References: <20180717142314.32337-1-alexandre.belloni@bootlin.com> <20180717142314.32337-2-alexandre.belloni@bootlin.com> <20180717214212.GE3211@piout.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.0 (2018-05-17) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 18/07/2018 00:54:21+0300, Andy Shevchenko wrote: > On Wed, Jul 18, 2018 at 12:42 AM, Alexandre Belloni > wrote: > > On 18/07/2018 00:30:49+0300, Andy Shevchenko wrote: > >> On Wed, Jul 18, 2018 at 12:30 AM, Andy Shevchenko > >> wrote: > >> > On Tue, Jul 17, 2018 at 5:23 PM, Alexandre Belloni > >> > wrote: > >> > >> > Reviewed-by: Andy Shevchenko > >> > > >> >> Signed-off-by: Alexandre Belloni > >> > >> Shouldn't it have a Fixes tag? > >> > > > > Well, I'm not sure how far this can be backported. It also seems nobody > > ever hit that while our hardware will hit it at every boot. > > > > I'll try to find out. > > No-one enabled CONFIG_DEBUG_SHIRQ? > Nope, this is a real HW IRQ. I meant find out up to when it can be sanely backported. -- Alexandre Belloni, Bootlin (formerly Free Electrons) Embedded Linux and Kernel engineering https://bootlin.com