From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755441AbbAORET (ORCPT ); Thu, 15 Jan 2015 12:04:19 -0500 Received: from mail-ig0-f177.google.com ([209.85.213.177]:50134 "EHLO mail-ig0-f177.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753124AbbAORER (ORCPT ); Thu, 15 Jan 2015 12:04:17 -0500 MIME-Version: 1.0 In-Reply-To: <1421156505-16600-4-git-send-email-semen.protsenko@globallogic.com> References: <1421156505-16600-1-git-send-email-semen.protsenko@globallogic.com> <1421156505-16600-4-git-send-email-semen.protsenko@globallogic.com> Date: Thu, 15 Jan 2015 18:04:16 +0100 Message-ID: Subject: Re: [PATCH 3/4] gpio: max732x: Fix possible deadlock From: Linus Walleij To: Semen Protsenko Cc: Alexandre Courbot , Grant Likely , Mark Rutland , "linux-gpio@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "devicetree@vger.kernel.org" , Marc Zyngier , Grygorii Strashko , Illia Smyrnov Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Jan 13, 2015 at 2:41 PM, Semen Protsenko wrote: > This patch was derived from next one: > "gpio: fix pca953x set_type 'scheduling while atomic' bug". > > After adding entry that consumes max732x GPIO as interrupt line to dts > file, deadlock appears somewhere in max732x probe function. Patch applied. Yours, Linus Walleij