From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tejun Heo Subject: Re: [PATCH] pata_legacy: Allow disabling of legacy PATA device probes on non-PCI systems Date: Thu, 22 Dec 2016 12:19:02 -0500 Message-ID: <20161222171902.GC31216@htj.duckdns.org> References: <20161202170705.GB6033@htj.duckdns.org> <20161205192310.GA30331@mtj.duckdns.org> <20161212170154.GA13864@htj.duckdns.org> <20161222163711.GB29161@htj.duckdns.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from mail-yw0-f194.google.com ([209.85.161.194]:33199 "EHLO mail-yw0-f194.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S965341AbcLVRTE (ORCPT ); Thu, 22 Dec 2016 12:19:04 -0500 Received: by mail-yw0-f194.google.com with SMTP id s68so15229313ywg.0 for ; Thu, 22 Dec 2016 09:19:04 -0800 (PST) Content-Disposition: inline In-Reply-To: Sender: linux-ide-owner@vger.kernel.org List-Id: linux-ide@vger.kernel.org To: whiteheadm@acm.org Cc: One Thousand Gnomes , Sergei Shtylyov , linux-ide@vger.kernel.org Hello, On Thu, Dec 22, 2016 at 12:14:43PM -0500, tedheadster wrote: > It looks to me that when something is 'platform' it is not expected to > ever go away, and that generally includes irqs. There are calls to > platform_get_irq() but there isn't even a function called > platform_put_irq() or platform_free_irq(). But it works fine if we open and release an explicit devres group, so the problem isn't there. The problem is why platform device destruction isn't triggering devres release of all associated resources. Thanks. -- tejun